View PSB7115FV21_781834.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

ics for communications enhanced isdn data access controller isar 34 psb 7115 version 2.1 firmware version 1.01 data sheet 02.98 ds 2
edition 02.98 this edition was realized using the software system framemaker a . published by siemens ag, hl sp, balanstra?e 73, 81541 mnchen ? siemens ag 1998. all rights reserved. attention please! as far as patents or other rights of third parties are concerned, liability is only assumed for components, not for application s, processes and circuits implemented within components or assemblies. the information describes the type of component and shall not be considered as assured characteristics. terms of delivery and rights to change design reserved. for questions on technology, delivery and prices please contact the semiconductor group offices in germany or the siemens compa nies and representatives worldwide (see address list). due to technical requirements components may contain dangerous substances. for information on the types in question please cont act your nearest siemens office, semiconductor group. siemens ag is an approved cecc manufacturer. packing please use the recycling operators known to you. we can also help you C get in touch with your nearest sales office. by agreeme nt we will take packing material back, if it is sorted. you must bear the costs of transport. for packing material that is returned to us unsorted or which we are not obliged to accept, we shall have to invoice you for an y costs incur- red. components used in life-support devices or systems must be expressly authorized for such purpose! critical components 1 of the semiconductor group of siemens ag, may only be used in life-support devices or systems 2 with the express written approval of the semiconductor group of siemens ag. 1 a critical component is a component used in a life-support device or system whose failure can reasonably be expected to cause the failure of that life-support device or system, or to affect its safety or effectiveness of that device or system. 2 life support devices or systems are intended (a) to be implanted in the human body, or (b) to support and/or maintain and sust ain hu- man life. if they fail, it is reasonable to assume that the health of the user may be endangered. psb 7115 revision history: current version: 02.98 previous version: 09.97 page (in previous version) page (in current version) subjects (major changes since last revision) 247/248 256/257 external memory interface timings added - 188-196 general purpose i/os added 126 126 16 bit data path added 173 173 tsl=011 mode removed iom ? , iom ? -1, iom ? -2, sicofi ? , sicofi ? -2, sicofi ? -4, sicofi ? -4c, slicofi ? , arcofi ? , arcofi ? -ba, arcofi ? -sp, epic ? -1, epic ? -s, elic ? , ipat ? -2, itac ? , isac ? -s, isac ? -s te, isac ? -p, isac ? -p te, idec ? , sicat ? , octat ? -p, quat ? -s are registered trademarks of siemens ag. musac ? -a, falc ? 54, iwe ? , sare ? , utpt ? , asm ? , asp ? are trademarks of siemens ag.
psb 7115 table of contents page semiconductor group 3 02.98 1 general information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 1.2 system integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 1.2.1 isdn pc/workstation adapter with s-interface . . . . . . . . . . . . . . . . . . . .13 1.2.2 isdn pc / workstation adapter with u-interface . . . . . . . . . . . . . . . . . . .14 1.2.3 isdn pc / workstation adapter as intelligent nt . . . . . . . . . . . . . . . . . . .15 1.2.4 isdn voice/data terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 1.2.5 fax/modem pool with primary rate access . . . . . . . . . . . . . . . . . . . . . . .17 1.3 logic symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 1.4 device architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 1.5 pin configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 1.5.1 pin description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 2 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 2.1 functional overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 2.2 clock generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 2.3 physical interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 2.3.1 host interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 2.3.2 iom ? -2 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 2.3.3 sai interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 2.3.4 external memory interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 2.3.5 general purpose i/o interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 2.4 communications interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 2.5 functional blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 2.5.1 buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 2.5.2 sart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 2.5.2.1 hdlc mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 2.5.2.2 async mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 2.5.2.3 binary mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 2.5.3 pump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 2.5.3.1 fax modulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 2.5.3.2 datamodem modulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 2.5.3.3 halfduplex modulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 2.5.3.4 v.110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 2.5.3.5 dtmf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 2.5.3.6 bypass mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 2.5.4 iom ? -2 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 2.5.5 d-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 2.5.6 c/i-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 2.5.7 tic-bus access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 2.5.8 monitor channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 3 operational description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
psb 7115 table of contents page semiconductor group 4 02.98 3.1 host communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 3.1.1 message structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 3.1.2 interrupt status byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 3.1.3 control registers and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 3.1.4 configuration after reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 3.1.5 message transfer from host to isar 34 . . . . . . . . . . . . . . . . . . . . . . . . . .72 3.1.6 message transfer from isar 34 to host . . . . . . . . . . . . . . . . . . . . . . . . . .74 3.1.7 message overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 3.2 buffer configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 3.2.1 buffer configuration setup (host ? isar 34) . . . . . . . . . . . . . . . . . . . . .79 3.2.2 buffer configuration request (host ? isar 34) . . . . . . . . . . . . . . . . . . .81 3.2.3 buffer configuration response (isar 34 ? host) . . . . . . . . . . . . . . . . . .82 3.2.4 buffer control command (host ? isar 34) . . . . . . . . . . . . . . . . . . . . . . .84 3.3 buffer status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 3.3.1 buffer status request (host ? isar 34) . . . . . . . . . . . . . . . . . . . . . . . . .85 3.3.2 buffer status response (isar 34 ? host) . . . . . . . . . . . . . . . . . . . . . . . .87 3.3.3 buffer status event (isar 34 ? host) . . . . . . . . . . . . . . . . . . . . . . . . . . .89 3.3.3.1 buffer specific status event (isar 34 ? host) . . . . . . . . . . . . . . . . . . . .89 3.3.3.2 buffer general status event (isar 34 ? host) . . . . . . . . . . . . . . . . . . . .90 3.4 sart configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 3.4.1 sart configuration setup - hdlc (host ? isar 34) . . . . . . . . . . . . . . .92 3.4.2 sart configuration setup - async (host ? isar 34) . . . . . . . . . . . . . .94 3.4.3 sart configuration setup - binary (host ? isar 34) . . . . . . . . . . . . . . .97 3.4.4 sart configuration setup - disable sart (host ? isar 34) . . . . . . . . .99 3.5 sart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 3.5.1 sart status events with receive data (isar 34 ? host) . . . . . . . . . .100 3.5.1.1 sart status events with receive data - hdlc (isar 34 ? host) . . . .101 3.5.1.2 sart status events with receive data - async (isar 34 ? host) . .103 3.5.1.3 sart status events with receive data - binary (isar 34 ? host) . . . .104 3.5.2 sart control commands with transmit data (host ? isar 34) . . . . .105 3.5.2.1 sart control commands with transmit data - hdlc (host ? isar 34) . . 105 3.5.2.2 sart control commands with transmit data - async (host ? isar 34) . 107 3.5.2.3 sart control commands with transmit data - binary (host ? isar 34) . . 109 3.6 pump configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 3.6.1 pump configuration setup (host ? isar 34) . . . . . . . . . . . . . . . . . . . . .110 3.6.1.1 pump configuration setup - fax modulations (host ? isar 34) . . . . . .112 3.6.1.2 pump configuration setup - datamodem modulations (host ? isar 34) . . 114 3.6.1.3 pump configuration setup - halfduplex modulations (host ? isar 34) 118
psb 7115 table of contents page semiconductor group 5 02.98 3.6.1.4 pump configuration setup - v.110 (host ? isar 34) . . . . . . . . . . . . . .121 3.6.1.5 pump configuration setup - dtmf (host ? isar 34) . . . . . . . . . . . . . .123 3.6.1.6 pump configuration setup - bypass mode (host ? isar 34) . . . . . . . .126 3.6.2 pump control command (host ? isar 34) . . . . . . . . . . . . . . . . . . . . . .127 3.6.2.1 pump control command - fax modulations (host ? isar 34) . . . . . . .128 3.6.2.2 pump control command - datamodem modulations (host ? isar 34) 131 3.6.2.3 pump control command - halfduplex modulations (host ? isar 34) . .131 3.6.2.4 pump control command - v.110 (host ? isar 34) . . . . . . . . . . . . . . . .132 3.6.2.5 pump control command - dtmf (host ? isar 34) . . . . . . . . . . . . . . .135 3.6.2.6 pump control command - bypass mode (host ? isar 34) . . . . . . . . .136 3.6.2.7 pump control command - c/i-channel (host ? isar 34) . . . . . . . . . . .137 3.7 pump status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 3.7.1 pump status request (host ? isar 34) . . . . . . . . . . . . . . . . . . . . . . . .139 3.7.2 pump status response (isar 34 ? host) . . . . . . . . . . . . . . . . . . . . . . .140 3.7.2.1 pump status response - fax modulations (isar 34 ? host) . . . . . . . .140 3.7.2.2 pump status response - datamodem modulations (isar 34 ? host) .142 3.7.2.3 pump status response - halfduplex modulations (isar 34 ? host) . .146 3.7.2.4 pump status response - v.110 (isar 34 ? host) . . . . . . . . . . . . . . . .148 3.7.2.5 pump status response - dtmf (isar 34 ? host) . . . . . . . . . . . . . . . .152 3.7.2.6 pump status response - bypass mode (isar 34 ? host) . . . . . . . . . .153 3.7.2.7 pump status response - pump disabled (isar 34 ? host) . . . . . . . . .154 3.7.3 pump status events (isar 34 ? host) . . . . . . . . . . . . . . . . . . . . . . . . .155 3.7.3.1 pump status events - fax modulations (isar 34 ? host) . . . . . . . . . . .155 3.7.3.2 pump status events - datamodem modulations (isar 34 ? host) . . . .157 3.7.3.3 pump status events - halfduplex modulations (isar 34 ? host) . . . . .158 3.7.3.4 pump status events - v.110 (isar 34 ? host) . . . . . . . . . . . . . . . . . . .159 3.7.3.5 pump status events - dtmf (isar 34 ? host) . . . . . . . . . . . . . . . . . . .163 3.7.3.6 pump status events - bypass mode (isar 34 ? host) . . . . . . . . . . . . .164 3.7.3.7 pump status events - d- and c/i-channel (isar 34 ? host) . . . . . . . .165 3.8 iom ? -2 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166 3.8.1 iom -2 configuration setup - path 1 and 2 (host ? isar 34) . . . . . . . .166 3.8.2 iom -2 configuration setup - path 3 (host ? isar 34) . . . . . . . . . . . . .169 3.8.3 iom -2 configuration request (host ? isar 34) . . . . . . . . . . . . . . . . . .170 3.8.4 iom -2 configuration response - general code (isar 34 ? host) . . .171 3.8.5 iom -2 configuration response - path 1 and 2 (isar 34 ? host) . . . . .172 3.8.6 iom -2 configuration response - path 3 (isar 34 ? host) . . . . . . . . .175 3.8.7 iom -2 control commands - general code (host ? isar 34) . . . . . . . .176 3.8.8 iom -2 control commands - path 1 and 2 (host ? isar 34) . . . . . . . . .178 3.8.9 iom -2 status events (isar 34 ? host) . . . . . . . . . . . . . . . . . . . . . . . . .180 3.9 monitor channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181 3.9.1 buffer configuration and status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181 3.9.2 monitor channel configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
psb 7115 table of contents page semiconductor group 6 02.98 3.9.2.1 monitor channel configuration setup (host ? isar 34) . . . . . . . . . .182 3.9.2.2 monitor channel configuration request (host ? isar 34) . . . . . . . .184 3.9.2.3 monitor channel configuration response (isar 34 ? host) . . . . . .184 3.9.3 monitor channel data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 3.9.3.1 monitor channel receive data (isar 34 ? host) . . . . . . . . . . . . . . .185 3.9.3.2 monitor channel transmit data (host ? isar 34) . . . . . . . . . . . . . .186 3.9.3.3 monitor channel status events (isar 34 ? host) . . . . . . . . . . . . . .187 3.10 gpio (general purpose i/os) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188 3.10.1 gpio configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189 3.10.1.1 gpio configuration - output register set/reset (host ? isar 34) . . .189 3.10.1.2 gpio configuration - direction (host ? isar 34) . . . . . . . . . . . . . . . . .191 3.10.1.3 gpio configuration - open drain select (host ? isar 34) . . . . . . . . . .192 3.10.1.4 gpio configuration - strobed input (host ? isar 34) . . . . . . . . . . . . . .193 3.10.1.5 gpio configuration - interrupt mask (host ? isar 34) . . . . . . . . . . . . .195 3.10.2 gpio status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197 3.10.2.1 gpio status request (host ? isar 34) . . . . . . . . . . . . . . . . . . . . . . . .197 3.10.2.2 gpio status event/response (isar 34 ? host) . . . . . . . . . . . . . . . . . .198 3.11 test/diagnostics path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199 3.11.1 timer interrupt on/off(host ? isar 34) . . . . . . . . . . . . . . . . . . . . . . . . .199 3.11.2 timer interrupt event (isar 34 ? host) . . . . . . . . . . . . . . . . . . . . . . . . .200 3.11.3 chip version request (host ? isar 34) . . . . . . . . . . . . . . . . . . . . . . . .201 3.11.4 chip version response (isar 34 ? host) . . . . . . . . . . . . . . . . . . . . . . .201 3.11.5 software version request (host ? isar 34) . . . . . . . . . . . . . . . . . . . . .202 3.11.6 software version response (isar 34 ? host) . . . . . . . . . . . . . . . . . . .202 3.11.7 request selftest result (isar 34 ? host) . . . . . . . . . . . . . . . . . . . . . . .203 3.11.8 selftest response (isar 34 ? host) . . . . . . . . . . . . . . . . . . . . . . . . . . .203 3.11.9 soft reset (host ? isar 34) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204 3.11.10 invalid message received (isar 34 ? host) . . . . . . . . . . . . . . . . . . . . .205 3.12 dsp program download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206 3.12.1 structure of file header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208 3.12.2 structure of block header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210 3.12.3 structure of data blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212 3.12.3.1 jump to block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212 3.12.3.2 write message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213 3.12.3.3 wait for next message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215 3.12.3.4 wait for specific message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217 3.12.3.5 compare last message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219 3.12.3.6 set coding information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221 3.12.3.7 set status information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222 3.12.3.8 write to memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223 3.13 fax class 1 implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225 3.13.1 summary of isar 34 fax control commands . . . . . . . . . . . . . . . . . . . .226
psb 7115 table of contents page semiconductor group 7 02.98 3.13.2 summary of isar 34 fax status events . . . . . . . . . . . . . . . . . . . . . . . . .227 3.13.3 procedure termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228 3.13.4 fax pump startup procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229 3.13.5 hdlc transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230 3.13.6 binary transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231 3.13.7 hdlc reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232 3.13.8 binary reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233 3.13.9 call termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234 3.13.10 procedure terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234 3.14 startup procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235 3.14.1 v.8 negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235 3.14.2 automode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236 4 summary of messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239 5 example configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243 6 detailed register description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 6.1 register address map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 6.2 register description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 7 electrical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 7.1 absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 7.2 recommended operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . .251 7.3 dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252 7.4 capacitances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253 7.5 oscillator circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253 7.6 xtal1,2 recommended typical crystal parameters . . . . . . . . . . . . . . .253 7.7 ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254 7.7.1 testing waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254 7.7.2 parallel host interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254 7.7.3 external memory interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258 7.7.4 iom ? -2 interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260 8 package outlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
psb 7115 list of figures page semiconductor group 8 02.98 figure 1: isdn pc/workstation adapter with s-interface . . . . . . . . . . . . . . . . . . . . 13 figure 2: isdn pc/workstation adapter with u-interface . . . . . . . . . . . . . . . . . . . . 14 figure 3: isdn pc/workstation adapter as intelligent nt . . . . . . . . . . . . . . . . . . . 15 figure 4: isdn voice/data terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 figure 5: fax/modem pool with primary rate access . . . . . . . . . . . . . . . . . . . . . . 17 figure 6: logic symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 figure 7: device architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 figure 8: pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 figure 9: functional block diagram of the isdn data access controller . . . . . . . . 28 figure 10: clock generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 figure 11: clock mode applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 figure 12: register access in multiplexed and non-multiplexed mode. . . . . . . . . . . 33 figure 13: linecard mode of the iom-2 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 figure 14: terminal mode of the iom-2 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 figure 15: memory configuration - dsp program download . . . . . . . . . . . . . . . . . . 36 figure 16: general purpose i/o interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 figure 17: interrupt input signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 figure 18: host interface registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 figure 19: structure of interrupt status byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 figure 20: mailbox interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 figure 21: communication buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 figure 22: structure of datapath buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 figure 23: hdlc data formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 figure 24: async data formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 figure 25: binary data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 figure 26: fax modulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 figure 27: fax class 1 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 figure 28: datamodem modulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 figure 29: halfduplex modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 figure 30: v.110 formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 figure 31: dtmf detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 figure 32: pump in bypass mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 figure 33: iom-2 configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 figure 34: tic-bus application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 figure 35: structure of last octet within ch2 on du . . . . . . . . . . . . . . . . . . . . . . . . 57 figure 36: structure of last octet within ch2 on dd . . . . . . . . . . . . . . . . . . . . . . . . 58 figure 37: monitor channel applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 figure 38: host communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 figure 39: message transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 figure 40: control registers and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 figure 41: initialisation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 figure 42: write message transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
psb 7115 list of figures page semiconductor group 9 02.98 figure 43: read message transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 figure 44: message directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 figure 45: binary file structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 figure 46: pointer on data structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 figure 47: download process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 figure 48: block header process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 figure 49: data block process - jump to block . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 figure 50: data block process - write message . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 figure 51: data block process - wait for next message. . . . . . . . . . . . . . . . . . . . . 216 figure 52: data block process - wait for specific message . . . . . . . . . . . . . . . . . . 218 figure 53: data block process - compare last message. . . . . . . . . . . . . . . . . . . . 220 figure 54: data block process - set coding information . . . . . . . . . . . . . . . . . . . . 221 figure 55: data block process - set status information . . . . . . . . . . . . . . . . . . . . . 222 figure 56: data block process - write to memory. . . . . . . . . . . . . . . . . . . . . . . . . . 224 figure 57: fax class 1 - startup procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 figure 58: fax class 1 - hdlc transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 figure 59: fax class 1 - binary transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 figure 60: fax class 1 - hdlc reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 figure 61: fax class 1 - binary reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 figure 62: fax class 1 - call termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 figure 63: fax class 1 - procedure terminations . . . . . . . . . . . . . . . . . . . . . . . . . . 234 figure 64: v.8 answering mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 figure 65: v.8 originating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 figure 66: automode answerer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 figure 67: automode originator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 figure 68: oscillator circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 figure 69: testing input/output waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 figure 70: microprocessor read timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 figure 71: microprocessor write timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 figure 72: multiplexed address timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 figure 73: non-multiplexed address timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 figure 74: microprocessor read timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 figure 75: microprocessor write timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 figure 76: non-multiplexed address timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 figure 77: external memory interface - write cycle . . . . . . . . . . . . . . . . . . . . . . . . 258 figure 78: external memory interface - read cycle . . . . . . . . . . . . . . . . . . . . . . . . 258 figure 79: iom ? -2 timing with double rate dcl. . . . . . . . . . . . . . . . . . . . . . . . . . . 260
psb 7115 list of tables page semiconductor group 10 02.98 table 1: clock mode settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 table 2: host interface signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 table 3: bus operation modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 table 4: buffer size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 table 5: his structure - path 1, 2 and 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 table 6: his structure - path 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 table 7: iis structure - path 1, 2 and 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 table 8: iis structure - path 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 table 9: configuration parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 table 10: pump modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 table 11: pump modes in path 1 and 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 table 12: v.110 remote dte status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 table 13: structure of file header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208 table 14: structure of block header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210 table 15: types of data blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210 table 16: block structure - block_type = 1h . . . . . . . . . . . . . . . . . . . . . . . . . . .212 table 17: block structure - block_type = 2h . . . . . . . . . . . . . . . . . . . . . . . . . . .213 table 18: block structure - block_type = 3h . . . . . . . . . . . . . . . . . . . . . . . . . . .215 table 19: block structure - block_type = 4h . . . . . . . . . . . . . . . . . . . . . . . . . . .217 table 20: block structure - block_type = 5h . . . . . . . . . . . . . . . . . . . . . . . . . . .219 table 21: block structure - block_type = 6h . . . . . . . . . . . . . . . . . . . . . . . . . . .221 table 22: block structure - block_type = 7h . . . . . . . . . . . . . . . . . . . . . . . . . . .222 table 23: types of memory write data blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . .223 table 24: block structure - block_type = 20h, 21h, 30h, 31h . . . . . . . . . . . . .223 table 25: fax class 1 - procedure termination. . . . . . . . . . . . . . . . . . . . . . . . . . . .228
psb 7115 general information semiconductor group 11 02.98 1 general information the isar 34, isdn data access controller forms an advanced solution for isdn applications communicating with remote isdn as well as analog terminals. the isar 34 psb 7115 follows its predecessor isar psb 7110 which is capable of modem modulation up to 14400 bit/s (v.32bis). the new isar 34 has the similar functional architecture and additionally supports modem modulation up to 33600 bit/s (v.34bis). as well the platform is upgradeable to new modem standards (pcm modems) and is able to run algorithms for audio compression (e.g. g.728) or answering machine alternatively. a special version called "isar ac" is available for this purpose the isar 34 is designed for data access over isdn. it can be used in data terminals combining isdn and analog functionality for communication with remote subscribers. it can also be integrated in fax/modem pools and routers. the isar ac version fits perfectly into h.320/h.324 video conferencing systems, in which it supports both the modem and audio functions. it integrates two data formatting units which support binary framing, hdlc and async, which is an asynchronous data formatting according to itu-t v.14. the data from the formatting units is input data to a fax/modem modulation or v.110 or transparent framing towards the iom-2 timeslots. as well one channel dtmf generation and detection is supported in the data pump. the isar 34 operates on the iom-2 interface in terminal mode (1.536 mhz dcl) and is also designed to operate on line-card iom-2 interfaces (4.096 mhz dcl). as the dsp program is downloaded into external memory connected to the memory interface of the isar 34, firmware upgrades for new algorithms and future applications are quite easy to realize. for example a further version will fully provide a codec interface to support the siemens analog line interface solution alis for analog modem applications. an elaborate mailbox interface with 256 byte buffers in each direction reduces the number of registers to a minimum. the psb 7115 isdn data access controller is a cmos device offered in a thin quad- flat pack package. it operates from a single 3.3 v supply and the inputs are 5v safe.
p-tqfp-144-2 semiconductor group 12 02.98 enhanced isdn data access controller isar 34 psb 7115 version 2.1 cmos type ordering code package psb 7115 f v2.1 p-tqfp-144-2 1.1 features ? modem modulation up to 33600 bit/s (v.34bis) including fallback modes ? fax modulation up to 14400 bit/s (v.17) including fallback modes ? bit rate adaptation according to v.110 for both b- channels (except during datamodem modulation) ? dtmf generation and detection in one channel ? two universal formatters supporting async (itu-t v.14), hdlc and binary framing of data for b- channel applications ? v.8 rate negotiation ? isdn d-channel hdlc controller with tic bus support ? isdn c/i-channel and monitor channel handler ? iom-2 terminal mode (1.536 mhz), line card mode (4.096 mhz) ? mailbox interface for host communication ? external memory interface to connect external program and data memory ? upgradeable to new technologies (e.g. pcm modem) ? 256 byte fifo per direction for host interface communication of b-channel data ? 9 programmable general purpose i/o lines ? on-chip pll for clock generation ? 3.3 v power supply ? thin qfp-package ? advanced cmos technology
psb 7115 general information semiconductor group 13 02.98 1.2 system integration 1.2.1 isdn pc/workstation adapter with s-interface the isdn pc or workstation adapter is based on the isar 34. a psb 2186, isac-s te forms the s-transceiver and the isar 34 provides the hdlc controller to perform the d- channel signalling protocol. external circuitry is required for the s-interfaces which includes the transformer and protection circuitry. the host interface of the isar 34 is connected to the host bus. figure 1 isdn pc/workstation adapter with s-interface the isar 34 supports hdlc based applications like file transfer, access to packet switches (x.75, v.120, ppp). it also supports communication to terminal adapters which perform bit rate adaptation according to v.110. a special feature of the isar 34 is its support for analog fax/modem applications. therefore, pcm data is converted to linear data and handled by a v.34bis/v.17 data pump to support data rates up to 33600 bit/s (v.34bis) and 14400 bit/s (v.17).
psb 7115 general information semiconductor group 14 02.98 1.2.2 isdn pc / workstation adapter with u-interface especially for the us market the u-interface formed by the psb 21910 iec-q nte, is considered as the standard basic rate interface. the isar 34 supports these applications in a cost effective way since it includes the d-channel hdlc controller, the command/indicate channel as well as the monitor channel. the iom-2 interface supports tic bus access. figure 2 isdn pc/workstation adapter with u-interface
psb 7115 general information semiconductor group 15 02.98 1.2.3 isdn pc / workstation adapter as intelligent nt a variation of the u-interface pc card is called the intelligent nt since it provides the network termination function as part of the card. the isar 34 supports the tic bus of the iom-2 interface which controls the d-channel data flow between the local d-channel source inside the isar 34 and the d-channel sources on the s-interface. the intc-q peb 8191 is the integration of the s- and u- transceivers, dedicated to intelligent nt applications. figure 3 isdn pc/workstation adapter as intelligent nt
psb 7115 general information semiconductor group 16 02.98 1.2.4 isdn voice/data terminal figure 4 shows a voice data terminal developed on a pc card, where the isar 34 provides its fax and modem functionality within a three chip solution. during isdn calls the arcofi-sp psb 2163 provides for speakerphone functions and includes an additional dtmf generator. figure 4 isdn voice/data terminal
psb 7115 general information semiconductor group 17 02.98 1.2.5 fax/modem pool with primary rate access figure 5 shows an application suitable for modem pools or fax servers (fax on demand). the frame and line interface controller falc 54 peb 2254 provides for direct access to the pcm highway, may be programmed to operate in 1.544 mbit/s (pcm24, t1) or 2.048 mbit/s (pcm30/e1) carrier systems and provides the complete functionality of a line interface-, framing-, clock generation- and signalling unit. the selection of timeslots on the isar 34 is programmable, so they are cascadable in any order. depending on whether or not the microprocessor performs a download to external sram of the isar 34, flash memory may be required or not. figure 5 fax/modem pool with primary rate access
psb 7115 general information semiconductor group 18 02.98 1.3 logic symbol figure 6 logic symbol dd du dcl fsc reset ca(0:17) cd(0:15) cwr crd iom-2 interface external memory interface xtal1 psb 7115 xtal2 csm1 cs parallel host interface int ad(0:7), d(0:7) rd wr ale vdd vss vddp power supply clko cm0 cm1 system clock interface vssa vdda a(0:7) csm2 csm3 csm0 7115_18 sr st rfs tfs serial audio interface (not supported in this version) sclk gp(0:14) general purpose i/o interface vssap vddap
psb 7115 general information semiconductor group 19 02.98 1.4 device architecture figure 7 device architecture cs int ad(0:7), d(0:7) rd wr ale ca(0:17) cd(0:15) cwr crd csm1 csm0 reset a(0:7) csm2 csm3 2 2 5 2
psb 7115 general information semiconductor group 20 02.98 1.5 pin configuration figure 8 pinout ale cs rd / ds wr / r/w ad7/d7 ad6/d6 ad5/d5 ad4/d4 vdd vss ad3/d3 ad2/d2 ad1/d1 ad0/d0 res. res. res. res. res. res. res. res. a7 a6 a5 a4 vdd vss a3 a2 a1 a0 int n.c. n.c. vddp 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 n.c. n.c. n.c. n.c. vss vdd cd0 ca0 cd1 ca1 cd2 ca2 vss vdd cd3 ca3 cd4 ca4 cd5 ca5 vss vdd cd6 ca6 cd7 ca7 cd8 ca8 vss vdd cd9 ca9 crd cwr csm3 csm2 psb 7115 v2.1 p-tqfp-144 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 gp14 gp13 gp12 vddp gp11 gp10 gp9 gp8 vdd vss gp7 gp6 gp5 gp4 gp3 gp2 gp1 gp0 clko reset vdd vss vdda xtal1 xtal2 vssa cm1 cm0 vddap vssap tfs rfs sclk st sr res. 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 csm1 csm0 vss vdd cd10 ca10 cd11 ca11 cd12 ca12 vss vdd cd13 ca13 cd14 ca14 cd15 ca15 vss vdd ca16 ca17 dd du dcl fsc n.c. n.c. res. res. res. vss vdd n.c. n.c. n.c.
psb 7115 general information semiconductor group 21 02.98 1.5.1 pin description pin no. symbol input (i) output (o) function parallel host interface 14 13 12 11 8 7 6 5 ad0/d0 ad1/d1 ad2/d2 ad3/d3 ad4/d4 ad5/d5 ad6/d6 ad7/d7 i/o i/o i/o i/o i/o i/o i/o i/o multiplexed bus mode: address/data bus transfers addresses and data between the host and the isar 34. demultiplexed bus mode: data bus transfers data between the host and the isar 34. 32 31 30 29 26 25 24 23 a0 a1 a2 a3 a4 a5 a6 a7 i i i i i i i i demultiplexed bus mode (only): address bus transfers address from the host to the isar 34. these pins are not used in multiplexed bus mode, therefore they should be tied to vdd in this mode. 3rd ds i i read this signal indicates a read operation. (siemens/intel bus mode). data strobe the rising edge marks the end of a valid read or write operation. (motorola bus mode). 4wr r/w i i write this signal indicates a write operation. (siemens/intel bus mode). read/write a "1" identifies a valid host access as a read operation. a "0" identifies the access as a write operation. (motorola bus mode). 2cs i chip select a "0" on this line selects the isar 34 for a read/write operation.
psb 7115 general information semiconductor group 22 02.98 1alei address latch enable a 1 on this line indicates an address on ad (0:7), that will be latched by the isar 34 (multiplexed mode only). this allows the isar 34 to be directly connected to a host with multiplexed address/data bus. ale also selects the interface mode (multiplexed or non-multiplexed). 33 int o (od) interrupt request this signal is activated, when the isar 34 requests an interrupt. this pin is an open drain output. iom a -2 interface 50 dd i/o data downstream on iom-2/pcm interface. 49 du i/o data upstream on iom-2/pcm interface. 48 dcl i/o data clock clock frequency is twice the data rate. 47 fsc i/o frame sync marks the beginning of a physical iom-2 or pcm frame. serial audio interface (not supported in this version) 141 sclk i/o serial clock serial clock for sr and st. 143 sr i/o serial data receive 142 st i/o serial data transmit 140 rfs i/o receive frame sync 139 tfs i/o transmit frame sync 1.5.1 pin description pin no. symbol input (i) output (o) function
psb 7115 general information semiconductor group 23 02.98 system clocks 132 xtal1 i crystal in or clock in if a crystal is used, it is connected across xtal1 and xtal2. if a clock signal is provided (via an external oscillator), this signal is input via xtal1. in this case the xtal2 output is to be left non-connected. 133 xtal2 o crystal out left unconnected if a crystal is not used. 136 135 cm0 cm1 i i clock mode select one of four different clock mode options can be selected by cm1,0 tied to vddp or vss. 127 clko o clock out a buffered output clock equal to the clock input at xtal1 is provided for further devices on the system. external memory interface 101 99 97 93 91 89 85 83 81 77 67 65 63 59 57 55 52 51 ca0 ca1 ca2 ca3 ca4 ca5 ca6 ca7 ca8 ca9 ca10 ca11 ca12 ca13 ca14 ca15 ca16 ca17 o o o o o o o o o o o o o o o o o o c-bus address used for addressing external program and data memory. 1.5.1 pin description pin no. symbol input (i) output (o) function
psb 7115 general information semiconductor group 24 02.98 102 100 98 94 92 90 86 84 82 78 68 66 64 60 58 56 cd0 cd1 cd2 cd3 cd4 cd5 cd6 cd7 cd8 cd9 cd10 cd11 cd12 cd13 cd14 cd15 i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o i/o c-bus data data bus for external program and data memory. 76 crd o c-bus read to external memory this signal must be connected to the rd input of the external program and data memory. 75 cwr o c-bus write to external memory this signal must be connected to the wr input of the external program and data memory. 71 72 73 74 csm0 csm1 csm2 csm3 o o o o c-bus select line for external memory bank #0, #1, #2, #3 this signal must be connected to the cs input of the corresponding memory bank. 1.5.1 pin description pin no. symbol input (i) output (o) function
psb 7115 general information semiconductor group 25 02.98 general control 128 reset i reset input 126 125 124 123 122 121 120 119 116 115 114 113 111 110 109 gp0 gp1 gp2 gp3 gp4 gp5 gp6 gp7 gp8 gp9 gp10 gp11 gp12 gp13 gp14 i/o general purpose input/output these pins serve as general purpose input/output lines with interrupt input capability. pins gp0-8 are programmable by host, pins gp9-14 are reserved for testing purpose. 1.5.1 pin description pin no. symbol input (i) output (o) function
psb 7115 general information semiconductor group 26 02.98 power supply 10 28 41 54 62 70 80 88 96 104 118 130 v ss v ss v ss v ss v ss v ss v ss v ss v ss v ss v ss v ss i i i i i i i i i i i i ground (common to v dd and v ddp ) 9 27 40 53 61 69 79 87 95 103 117 129 v dd v dd v dd v dd v dd v dd v dd v dd v dd v dd v dd v dd i i i i i i i i i i i i positive power supply voltage (3.0 - 3.6 v) 36 112 v ddp v ddp i i positive power supply voltage (4.5 - 5.5 v) 134 v ssa i separate analog ground (0 v) for clock generation unit. 131 v dda i separate analog positive power supply voltage (3.0 - 3.6 v) for clock generation unit. 1.5.1 pin description pin no. symbol input (i) output (o) function
psb 7115 general information semiconductor group 27 02.98 138 v ssap i separate analog ground (0 v) for pll. 137 v ddap i separate analog positive power supply voltage (3.0 - 3.6 v) pll. reserved pins 15 16 17 18 19 20 21 22 42 43 44 144 res. reserved these pins are reserved for further use. they must be connected to vdd. 34 35 37 38 39 45 46 105 106 107 108 n.c. not connected these pins are not used and may be left not connected. 1.5.1 pin description pin no. symbol input (i) output (o) function
psb 7115 functional description semiconductor group 28 02.98 2 functional description 2.1 functional overview figure 9 depicts the detailed functional architecture of the isar 34 v2.1: ? one modem/fax engine for v.34bis (33600 bit/s), v.17 (14400 bit/s), including fallback modes ? upgradeable to new modem standards due to flexible firmware download capability ? dtmf receiver / transmitter in one channel ? v.110 formatter in two channels (except during datamodem modulation) ? two universal formatters sart (synchronous asynchronous receiver transmitter) supporting async (itu-t v.14), hdlc and binary modes ? d-channel hdlc controller ? c/i and monitor channel handler ? iom-2 interface for terminal or line-card applications with tic bus support ? external memory interface for program and data memory ? communications mailbox with 256 bytes per direction figure 9 functional block diagram of the isdn data access controller local bus interface communication mailbox 2 x 256 bytes host interface pump fax modem v.17 data modem v.34bis v.110 dtmf trans- parent timeslot assignment sart async v.14 hdlc binary buffer 1 pump v.110 trans- parent timeslot assignment sart async v.14 hdlc binary buffer 2 tic bus access d-channel hdlc buffer 3 channel select buffer 0 c/i channel monitor channel test/ diag. 7115_21 bank 3 bank 2 bank 1 bank 0 ext. memory iom-2 interface sai interface * *) the sai interface is not supported in this version
psb 7115 functional description semiconductor group 29 02.98 2.2 clock generation the chip internal clocks are derived from a crystal connected across xtal1 and xtal2 or from an external clock input via pin xtal1. figure 10 clock generation one of four options can be used for the generation of the internal dsp master clock which is used for the fax/modem pump for example. other functional blocks derive their clock signal directly from the iom-2 interface. external memory, bank 0 transceiver interface logic (pnp, isa) or microcontroller power supply clock generation psb 7115 v2.1 bank 1 bank 2 bank 3 codec and daa * *) sai interface not supported in this version
psb 7115 functional description semiconductor group 30 02.98 an internal pll derives the dsp clock from a 7.68 mhz, 15.36 mhz or 16.384 mhz source at xtal1 (see table 1 ). in test mode the internal pll is bypassed and the dsp clock is directly provided at xtal1 . note: the clock mode cm1,0 = 11 is reserved for further use as the serial audio interface (sai) to connect the alis is not supported in this version. at clko a buffered output clock equal to the input clock at xtal1 is provided. this allows for hardware designs that only require one crystal for two or more devices on the system. the 7.68 mhz crystal is commonly used in terminal equipment with s-interface, e.g. the isar 34 together with the s-transceiver isac-s te psb 2186. one crystal is connected to the isar 34 and clko is connected to the xtal1 input of the isac-s te. for u-terminals a 15.36 mhz crystal is provided at the isar 34 and in the same way the u-transceiver iec-q te psb 21911 derives its input clock from clko. in analog modem applications with the alis a 16.384 mhz crystal provides the common clock for isar 34 and alis. this mode is reserved for further use. figure 11 clock mode applications table 1 clock mode settings cm1 cm0 clock at xtal1 comment 0 0 dsp clock test mode (pll bypassed) 0 1 7.68 mhz s-terminal applications 1 0 15.36 mhz u-terminal applications 1 1 16.384 mhz analog modem applications (alis) 7115_20
psb 7115 functional description semiconductor group 31 02.98 2.3 physical interfaces the isar 34 provides five physical interfaces which are described in the following chapters: ? host interface ? iom-2 interface ? serial audio interface - sai (not supported in this version) ? external memory interface ? general purpose i/o interface 2.3.1 host interface the isar 34 is programmed via an 8-bit parallel host interface (table 2 ) that can be operated in multiplexed or non-multiplexed bus mode. table 2 host interface signals symbol input (i) output (o) function ad(0:7) d(0:7) i/o address/data bus (multiplexed mode) transfers addresses and data between the host and the isar 34. data bus (non-multiplexed mode) transfers data between the host and the isar 34. a(0:7) i address bus (non-multiplexed mode) input address to the isar 34 registers. rd ds i read (siemens/intel bus mode) this signal indicates a read operation. data strobe (motorola bus mode) the rising edge marks the end of a valid read or write operation. wr r/w i write (siemens/intel bus mode) this signal indicates a write operation. read/write (motorola bus mode) a "1" identifies a valid host access as a read operation and a "0" identifies it as a write operation. cs i chip select a "0" on this line selects the isar 34 for a read/write operation.
psb 7115 functional description semiconductor group 32 02.98 the isar 34 provides three types of m p buses, which are selected via pin ale: the occurrence of an edge on ale, either positive or negative, at any time during the operation immediately selects the interface type 3. a return to one of the other interface types is possible only if a hardware reset is issued. note: if the multiplexed address/data bus type 3 is selected, the unused address pins a0-a7 must be tied to v dd . ale i address latch enable a 1 on this line indicates an address on ad (0:7), that is latched by the isar 34 (multiplexed mode only). ale also selects the interface mode (multiplexed or non- multiplexed). int o (od) interrupt request this is the interrupt output line to the host for all mailbox interrupt status requests. it is an open drain output. table 3 bus operation modes 1 ale tied to v dd motorola type with control signals cs , r/w , ds 2 ale tied to v ss siemens/intel non-multiplexed bus type with control signals cs , wr , rd 3 edge on ale siemens/intel multiplexed address/data bus type with control signals cs , wr , rd , ale table 2 host interface signals symbol input (i) output (o) function
psb 7115 functional description semiconductor group 33 02.98 since the mailbox structure of the isar 34 just requires 9 register locations, the host needs to decode only 4 address lines a0-3 in non-multiplexed bus mode while the other address lines a4-7 a re strapped to 0. if the software reset (bit rst) is not required only 3 address lines a0-2 need to be decoded (address 00h-07h). all remaining address locations (09h-ffh) are reserved for further use and should not be accessed by the host. figure 12 register access in multiplexed and non-multiplexed mode
psb 7115 functional description semiconductor group 34 02.98 2.3.2 iom a -2 interface the iom-2 interface is a 4-wire interface with two data lines (du and dd), a data clock (dcl) and a frame sync signal (fsc), of which the rising edge indicates the start of an iom-2 frame (8 khz). for iom-2 applications the data clock is typically set to twice the data rate. iom a -2 driver the output driver of the dd and du pins is selectable, open drain (default) or push pull. the output drivers are active for the selected time-slot bits and remain tri-state during the rest of the frame. the control lines fsc and dcl are input or output. iom a -2 frame structure/timing modes the isar 34 supports the iom-2 terminal and line-card mode. in terminal mode, the three channel iom-2 structure is used (see figure 14 ). in line-card mode (see figure 13 ), eight iom-2 channels can be programmed with flexible time-slot assignment of the b-channel data. figure 13 linecard mode of the iom-2 interface itd09635 ch1 ch2 ch3 ch4 ch5 ch6 ch7 ch0 ch0 ch7 ch6 ch5 ch4 ch3 ch2 ch1 b1 b2 monitor d c/i mm rx 125 fsc dcl dd du s iom ch0 iom ch0 r r
psb 7115 functional description semiconductor group 35 02.98 h figure 14 terminal mode of the iom-2 interface the isar 34 is able to make extensive use of the iom-2 channels as it is able to access all user data timeslots by programming the timeslot number and bit shift. the monitor channel is used for information exchange between the isar 34 and other devices connected to the iom-2 interface. in the c/i-channel real time status information is exchanged between the devices. both types of information transfer are supported by the isar 34 which provides a monitor and c/i-channel handler. in te mode the tic bus capability is implemented in the last octet of the third iom-2 channel (channel 2). this arbitration mechanism which allows the access of up to seven d-channel sources on the iom-2 interface, is implemented on the isar 34. for detailed information refer to the iom-2 interface reference guide. 2.3.3 sai interface the serial audio interface (sai) is not supported in this version, but in further versions of the isar 34. itd09636 tad dd b1 b2 mon0 ci0 ic1 ic2 mon1 ci1 d mr mx mx mr s/g fsc bac mr mx mx mr d ci1 mon1 ic2 ic1 ci0 mon0 b2 b1 du sds ch0 a/b 125 s iom -2 iom ch1 -2 iom ch2 -2 r r r
psb 7115 functional description semiconductor group 36 02.98 2.3.4 external memory interface external memory is required to store operational data and the dsp program. up to four memory banks with an address range of 256kx16 each can be addressed, however the specific memory configuration depends on the application. generally the platform is capable of the following options: operational data is stored in external sram whereas the storage of the dsp program code depends on the application. for pc based applications (e.g. plug in card) it can be downloaded into external sram, whereas for standalone systems (e.g. settop box) it is stored in non-volatile memory (e.g. flash), so no program download is necessary. the first version of isar 34, which is described in this specification, supports only the dsp program download mode. dsp program download the dsp program is downloaded from the host into the external memory of the isar 34. one memory bank of 128kx16, 15 ns is connected to csm0 (memory bank 0). the other memory banks (csm1-3 ) are not used. figure 15 memory configuration - dsp program download other memory configurations (e.g. dsp program in flash memory) can be supported in further versions of the isar 34.
psb 7115 functional description semiconductor group 37 02.98 2.3.5 general purpose i/o interface the isar 34 provides a general purpose i/o interface gpio that fulfils the requirements for different applications. each of the 15 pins can individually be programmed as an input or an output. as input they can additionally generate an interrupt. this interface can flexibly be used for general control functions or status indications from external devices. for example in modem applications hook switch and ring detect can be controlled via gpio-pins. all kind of data is exchanged between host and isar 34 in a message oriented way via the mailbox interface, i.e. the gpio pins are controlled via the dsp. the host releases messages to control the gpio interface, which are: ? output request: a logic 0 or 1 is output on the output port. ? input request: the status of the input port is requested. the isar 34 returns messages with the following information: ? input response: the status (0 or 1) of the input port is returned. ? input interrupt: a status change on the interrupt input port is indicated. figure 16 general purpose i/o interface
psb 7115 functional description semiconductor group 38 02.98 if enabled, a state change on input ports can initiate an interrupt to the host which is generated by the dsp. the status of the corresponding port is read by the host in a status indication message. the host programs whether a positive or negative signal edge on the input port will release an interrupt to the host ( figure 17 ). figure 17 interrupt input signal
psb 7115 functional description semiconductor group 39 02.98 2.4 communications interface the isar 34 provides a communications interface in terms of a 256 byte mailbox per direction, a 16 bit control word and an 8 bit interrupt register. besides that, there is a reset bit (bit 0 of register 08h), an interrupt mask/status bit (bit 2 of register 07h) and two interrupt acknowledge bits (lsb of address location 04h and 03h, respectively). the address map is shown in figure 18 , all other address locations are not used. figure 18 host interface registers software reset bit (08h write/read) the isar 34 is reset by setting and resetting this bit. it has a similar functionality as a hardware reset except this register itself is not affected and the reset pin is not activated, i.e. the software reset has only effect on the internal functions of the isar 34.
psb 7115 functional description semiconductor group 40 02.98 interrupt mask/status bit (07h write/read) all interrupt sources can be masked by setting the msk-bit to 0, so no interrupt is indicated to the host. the status sta-bit indicates whether an interrupt request is pending. if interrupt generation is disabled (msk=0), requests from the isar 34 can be recognized by polling the sta-bit. after reset the interrupt is not masked (msk=1), however, the mask bit affects only the generation of the interrupt, but not the interrupt status bit from being set. host/isar control registers the most significant byte of the control register (ctrl msb) contains configuration, status or control information depending on the type of message. the least significant byte (ctrl lsb) is used to indicate the number of bytes transferred via the mailbox (mailbox i/o data). these mailbox data may contain additional configuration, status or control information as well as receive/transmit data. host/isar interrupt status byte (his/iis) the interrupt status byte has a structure that defines the type of message, i.e. it contains information which buffer the message is related to and which functional block of the isar 34 the message is related to. figure 19 structure of interrupt status byte 7115_45 dps msc mds 7 6 5 4 3 2 1 0 message destination/source (buffer, sart, pump or iom-2) message coding defines the type of command datapath selection (path 0, 1, 2 or 3) his/iis note: the message structure is slightly different for test and diagnostics messages (datapath 0).
psb 7115 functional description semiconductor group 41 02.98 mailbox the mailbox is implemented as physically two separate 256-byte memory blocks which is seen from the host as an i/o device. thus, to read/write a byte from/to the mailbox, the host accesses a single location (mailbox i/o data), which is the same address but physically separate location for read and for write direction. the address is given by an address register directly programmable by the host (mailbox read/write address). this address is autoincremented every time an access by the host to mailbox i/o data is performed. thus, for sequential, fast access, the host only needs to set the start address for the first message byte and all subsequent data bytes can be read/written without reprogramming its address. for random access to the mailbox the host has to reprogram the address register(s). figure 20 mailbox interface d a t a d a t a host internal bus read address wr i t e address 256 byte 256 byte 02h 00h 02h 01h 7115_23
psb 7115 functional description semiconductor group 42 02.98 2.5 functional blocks the isar 34 host interface provides for merging/splitting of two data paths for b-channel data, one data path for d-channel data and c/i-channel access and a fourth data path for monitor channel data and exchange of test/diagnostics messages. each path is buffered both in read and write direction and the mailbox is used to access these four buffers. figure 21 communication buffers buffer 2 sart pump buffer size interrupts async hdlc binary v.110 transparent dtmf timeslot no. ts. width pcm coding buffer 1 sart pump iom-2 mail box buffer size interrupts async hdlc binary faxpump modempump v.110 transparent dtmf timeslot no. ts. width pcm coding buffer 3 sart iom-2 buffer size interrupts hdlc d-channel c/i-channel tic-bus buffer 0 iom-2 buffer size interrupts monitor channel iom chann e select 7115_2 4 iom-2 datapath 1 datapath 2 datapath 3 datapath 0
psb 7115 functional description semiconductor group 43 02.98 path 1 is used to access the fax/modem engine, a v.110 formatter, a dtmf generator/ detector or for transparent access to the iom-2 timeslots. path 2 is used to access a v.110 formatter or it provides transparent access to the iom- 2 timeslots. this datapath must not be configured to v.110 if path 1 is configured to datamodem modulations at the same time. path 1 and 2 integrate a sart (synchronous asynchronous receiver transmitter) which supports async, hdlc and binary mode. in async mode, the characters are formatted according to the itu-t v.14 standard by start, parity and stop bits. in hdlc mode, the hdlc bit level functions (flag, crc, zero-bit handling) are performed. binary mode describes a synchronous, transparent mode without formatting. path 3 incorporates an hdlc controller for d-channel data transfer and handles the access to the c/i-channel. the isar 34 supports the tic bus arbitration mechanism for those applications where several controllers are connected to the iom-2 interface. path 4 provides a monitor channel handler for information exchange with other devices. messages for test and diagnostics purposes are also transferred via this datapath. 2.5.1 buffer the mailbox represents the common host interface for all data paths, which are the two b-channel paths, the d- and c/i-channel path and the monitor channel and test/ diagnostics path. for each data path the read and write direction is buffered with a fifo (see figure 22 ). the complete buffer size for one data path is 2x256 byte (path 1, 2 and 3) or 2x64 byte (path 0) per direction. since the interrupt status byte and the control word is also transferred to the buffer by the isar 34, the available fifo space for user data is reduced by 3 bytes. so messages may contain a maximum number of user data of 253 or 61 byte, respectively. the maximum possible message length mpl for each path is shown in table 4 . dps is the d ata p ath s elect parameter in the host/isar interrupt status byte (his/iis) of each message. table 4 buffer size dps mpl buffer size (per direction) datapath 0 0 0 61 byte 2 x 64 byte datapath 1 0 1 253 byte 2 x 256 byte datapath 2 1 0 253 byte 2 x 256 byte datapath 3 1 1 253 byte 2 x 256 byte
psb 7115 functional description semiconductor group 44 02.98 figure 22 structure of datapath buffers buffer control after the host has written a message to the write buffer, the isar 34 will issue a buffer available interrupt to the host if there is still enough free buffer space for another message of the programmed length (i.e. another message may be written to the mailbox). if the host enters messages into the mailbox which exceed the configured message length, the fifo buffer may overflow and data might be lost. if there is no free space available , the isar 34 wont issue a data request message. the buffers can be set a priority to determine the sequence of service if several read buffers request for mailbox service simultaneously. write buffers read buffers mailbox read-/write buffers host datapath 0 datapath 1 datapath 2 datapath 3 write read 7115_25 256 256 2x256 2x256 2x256 2x256 2x256 2x256 2x64 2x64
psb 7115 functional description semiconductor group 45 02.98 2.5.2 sart the sart (synchronous asynchronous receiver transmitter) can be configured for async character formatting, hdlc bit level formatting and binary mode. i.e. no bit level formatting. in the figures below the serial audio interface sai is indicated as future upgrade. 2.5.2.1 hdlc mode in hdlc mode, the sart generates/handles the hdlc frame formatting. this includes opening and closing flag, crc generation/detection and zero-bit insertion (bit stuffing). figure 23 hdlc data formatting programmable features are: ? crc: 16 bit length, on/off ? inter frame timefill: '1' or flags ? bit stream coding: regular, inverse ? data underrun operation: abort generation/frame end (crc+flag) generation in transmit direction a frame is started after sart data is available in the transmit fifo buffer. the frame is continued until a frame end mark has been set in a mailbox command. in this case, the hdlc frame is closed by the crc value and a closing flag. in case a buffer underrun occurs, the current hdlc frame is closed either by an abort sequence or by crc and closing flag (programmable). in receive direction, hdlc frames exceeding the programmed message length are transferred to/from the buffer in data blocks of the configured message length. a message of reduced length may be transferred if a frame start, frame end or error condition is detected. in this case the control word contains the result of the crc check, verification of integer number of bytes and check of frame end condition.
psb 7115 functional description semiconductor group 46 02.98 2.5.2.2 async mode async denotes an asynchronous formatting of data according to itu-t specification v.14. in async mode, the sart adds/removes start, parity and stop bits to each data byte in transmit/receive direction. figure 24 async data formatting the following options are programmable: ? character length: 5, 6, 7, 8 bit ? no. of stop bits: 1,2 ? parity: no, odd, even, stick parity ? overspeed range: stop bit deletion: 1 of 8, 1 of 4 the async formatter supports overspeed handling according to v.14. therefore a stop bit may be deleted according to the overspeed range. the async formatter is able to generate a break signal and to detect a break signal of a minimum length of 2m+3 bits of start bit polarity. a special option is included to generate v.42 detection timing.
psb 7115 functional description semiconductor group 47 02.98 2.5.2.3 binary mode in binary mode no character formatting is performed. octets are transferred with the least significant bit or most significant bit first. figure 25 binary data programmable features are: ? idle character generation on data underrun ? bit swapping (lsb/msb first) in transmit direction, data from the transmit buffer is transmitted with the lsb or msb first. in case of data underrun, i.e. if there's no more data in the transmit buffer, a programmable byte or the last data byte is continuously transmitted. in receive direction, the data stream is received in octets. their contents is transferred to the receive buffer .
psb 7115 functional description semiconductor group 48 02.98 2.5.3 pump pump in general describes the additional formatting of the sart data (hdlc, async or binary) which is then forwarded to the iom-2 interface. in future versions pump data can also be transfered to the serial audio interface (sai). the pump modes are: ? fax modulations (v.17, ... ) ? datamodem modulations (v.34bis, .. ) ? halfduplex modulations ? v.110 ?dtmf ? bypass (transparent data) all pump modes are available in path 1, path 2 only supports v.110 and bypass mode. v.110 operation in data path 2 is not supported to run in parallel with datamodem modulations (full duplex modulations) in data path 1. in the figures below the serial audio interface sai is indicated as future upgrade. 2.5.3.1 fax modulations the mode fax modulations allows modulation up to v.17 (14400 bit/s). figure 26 fax modulations programmable parameters are: ? originating/answering mode ? enabling/disabling of answer/calling tone ? transmitter output attenuation ? modulation scheme (v.17, v.29, v.27ter, v.21 channel 2) set by control commands
psb 7115 functional description semiconductor group 49 02.98 in fax modulation mode the isar 34 supports the programming interface according to the fax class 1 standard eia/tia-578. during a fax call different kind of data is transmitted and received, which is hdcl framed data at low speed modulation (v.21ch2) for exchange of capabilities and call setup/shut down, and binary data at high speed modulation (v.17, v.29 or v.27ter) for document transmission. the host controls these configuration settings by simply issuing a pump control command (ftm, frm, fth, frh) that configures both the pump and the sart, i.e. the host does not need to reconfigure pump and sart separately for the individual fax procedures. figure 27 fax class 1 support
psb 7115 functional description semiconductor group 50 02.98 2.5.3.2 datamodem modulations this mode allows data modulation up to v.34bis (33600 bit/s). figure 28 datamodem modulations programmable parameters are: ? enabling/disabling of answer/calling tone ? transmitter output attenuation ? modulation scheme (v.34bis, v.32bis, v.32, v.23, v.22bis, v.22, v.21, bell 202, bell 212, bell 103 ) ? automode (eia/tia pn-2330) or dedicated mode ? modulation options according to the itu recommendations (fallback rates, retrain, renegotiate, etc. )
psb 7115 functional description semiconductor group 51 02.98 2.5.3.3 halfduplex modulations the halfduplex modulations allow modulation up to v.17 (14400 bit/s). in the figures below the serial audio interface sai is indicated as future upgrade. figure 29 halfduplex modulation programmable parameters are: ? enabling/disabling of receive/transmit direction ? enabling/disabling of echo protector tone ? transmitter output attenuation ? modulation scheme (v.17, v.29, v.27ter, v.21) the modulation schemes which are typically used for fax modulations can be programmed by the host without affecting the sart configuration (see chapter 2.5.3.1 ). in this way the host could handle a fax session by programming the sart and pump (halfduplex modulation) separately, however it is recommended to use the fax mode as it simplifies the control mechanisms of the host (no reconfiguration required).
psb 7115 functional description semiconductor group 52 02.98 2.5.3.4 v.110 the v.110 mode allows the framing of sart data for bit rate adaptation according to the itu-t recommendation v.110. figure 30 v.110 formatting the programmable features are: ? frame format/data rate ? e-, x-, s-bit control ? transmitter flow control (x-bits) ? remote dte status detection ? delay of synchronisation in transmit direction, the v.110 frame is combined with sart data and the state of e-, x- and s-bits. transmission of the last data byte in the mailbox is indicated to the host (buffer empty condition), which may set control bits. flow control by means of the x-bits is supported, which means that data transfer to the sart unit is stopped if indicated by the remote side. in receive direction, frame synchronization is monitored while the number of frames for synchronisation (normally 1) is programmable. the d-bits are forwarded to the sart and e-, x- and s- bits are forwarded to the host as status events any time they change their state. status conditions of the remote dte can be detected and indicated to the host. 0 0 0 0 0 0 0 0 1 d d d d d d s 1 d d d d d d x 1 d d d d d d s 1 d d d d d d s 1 e e e e e e e 1 d d d d d d s 1 d d d d d d x 1 d d d d d d s 1 d d d d d d s
psb 7115 functional description semiconductor group 53 02.98 2.5.3.5 dtmf the isar 34 supports dtmf generation and detection in one channel (two channels will be supported in the future). figure 31 dtmf detection dtmf mode allows transparent data transfer between sart unit and data pump while a dtmf detector is active, which indicates received dtmf tones to the host by means of status events. in order to send a dtmf tone (0, 1, 2, ... , 9, a, b, c, d, * , #) the host releases a control command to the isar 34. the programmable features are: ? rejection level (minimum required signal level to detect a dtmf tone) ? twist (maximum allowed level difference of the two frequencies) ? on duration of dtmf tone (1, 2, 3, ..., 255 ms) ? off duration after dtmf tone (1, 2, 3, ..., 255 ms) ? transmitter output attenuation
psb 7115 functional description semiconductor group 54 02.98 2.5.3.6 bypass mode the bypass mode allows the transparent transfer of a sart formatted digital data stream to the iom-2 timeslot without additional data formatting by the pump. in receive direction, data from the iom-2 timeslot is directly transferred to the sart. figure 32 pump in bypass mode
psb 7115 functional description semiconductor group 55 02.98 2.5.4 iom a -2 configuration the iom-2 configurations are separate for each datapath. via datapath 1 and 2, any timeslot for the output of pump data can be selected. the following programmable functions are available for path 1 and 2 ( figure 33 ): ? coding (a-law, m -law or 16-bit linear) ? timeslot position, i.e. start of timeslot ? length of timeslot (8 or 16 bit) ? switching of du/dd lines figure 33 iom-2 configuration parameters the host must ensure that the programmed timeslots on iom-2 for path 1 and path 2 do not overlap. datapath 3 is dedicated to the d-channel and the c/i-channel timeslot, respectively. the tic bus access handler which is used in terminal timing mode is operating on the tic bus channel (3rd channel) on iom-2. for the monitor channel handler in datapath 0 one of 16 iom-2 channels can be selected. the access is fixed to the third timeslot (monitor channel) of this channel.
psb 7115 functional description semiconductor group 56 02.98 2.5.5 d-channel the isar 34 provides an hdlc controller in datapath 3 which is responsible for the data link layer using hdlc based protocols (lapd). the data formatting in path 3 is fixed to hdlc framing, it is not programmable to binary or async as in path 1 and 2. the timeslot position is fixed to the d-channel timeslot on iom-2 (first two bits in fourth octett of iom-2 channel 0). the access to the fifo buffers for d-channel data is similar as for path 1 and 2. d-channel access can be performed with or without the tic-bus access mechanism (see chapter 2.5.7 ). 2.5.6 c/i-channel the command/indication channel carries real-time status information between the isar 34 and another device connected to the iom-2 interface. the isar 34 supports the 4-bit c/i0 channel, but it has no access to the 6-bit c/i1 channel. c/i0 conveys the commands and indications between the layer-1 device and the layer-2 parts of the isar 34 and it is used to control the layer-1 activation/deactivation procedures. access to c/i0 may be arbitrated via the tic bus access protocol (see chapter 2.5.7 ). in receive direction the code from layer-1 is continuously monitored and an interrupt is generated to the host anytime a change in the c/i-code is detected. a new code must be found in two consecutive iom-2 frames to be considered valid and to trigger a c/i-code change interrupt status (double last look criterion).
psb 7115 functional description semiconductor group 57 02.98 2.5.7 tic-bus access the tic-bus arbitration mechanism which is available in iom-2 te mode allows access of several external communication controllers (up to 7) to the layer-1 functions and to the d- and c/i-channel of the transceiver device ( figure 34 ). figure 34 tic-bus application the tic-bus is implemented in the last octet of iom channel 2 ( figure 35 and 36 ): figure 35 structure of last octet within ch2 on du 7115_ 3 icc peb 2070 transceiver iom-2 s/t or u isar 34 psb 7115 icc peb 2070 up to 7 d-channel controller
psb 7115 functional description semiconductor group 58 02.98 figure 36 structure of last octet within ch2 on dd in the case of an access request the isar 34 checks the bus accessed bit (bac) for the status "bus free", which is indicated by a logic "1". if the bus is free, the isar 34 transmits its individual tic-bus address and the bus is occupied by the device which sends its address error free. if more than one device attempt to seize the bus simultaneously, the one with the lowest address value wins. when the tic bus is seized by the isar 34 the bus is identified to other devices as occupied via the bac bit state "0" until the access request is withdrawn. after a successful bus access. the isar 34 is automatically set into a lower priority class, i.e. a new bus access cannot be performed until the status "bus free" is indicated in two successive frames. if none of the devices connected to the iom-2 interface request access to the d- and c/i-channels, the tic-bus address 7 will be present. the device with this address will therefore have access, by default, to the d- and c/i-channels. the bac bit is reset to state 1 when access to the c/i-channel is no longer requested, to grant other devices access to the d- and c/i-channels. the availability of the s/t interface d-channel is indicated in the stop/go bit (s/g): s/g=1: stop s/g=0: go the stop/go bit is available to other layer-2 devices connected to the iom-2 interface to determine if they can access the s/t bus d-channel. the available/blocked bit (a/b) is not influenced by the isar 34.
psb 7115 functional description semiconductor group 59 02.98 2.5.8 monitor channel the monitor channel protocol is a handshake protocol used for information exchange between the isar 34 and other devices. it is necessary for programming and controlling devices attached to the iom-2 interface, such like layer-1 transceivers (e.g. iec-q te psb 21911) or peripheral voice/data modules that do not need a parallel microcontroller interface (e.g. arcofi -sp psb 2163). figure 37 monitor channel applications the monitor channel operates on an asynchronous basis. while data transfers on the bus take place synchronized to frame sync, the flow of data is controlled by a handshake procedure using the monitor channel receive (mr) and monitor channel transmit (mx) bits. for example, data is placed onto the monitor channel and the mx bit is activated. this data will be transmitted repeatedly once per 8-khz frame until the transfer is acknowledged via the mr bit. mr and mx bits are controlled internally by the isar 34 according to the monitor channel protocol. 7115_ 3 isac-s te psb 2186 isar 34 psb 7115 arcofi-sp psb 2163 iom-2 monitor1 iec-q te psb 21911 isar 34 psb 7115 iom-2 monitor0 u s/t
psb 7115 operational description semiconductor group 60 02.98 3 operational description 3.1 host communication the communication between host and isar 34 is message oriented. that means all kind of information (b- and d-channel data, configuration data, status events, control commands, etc.) is exchanged by means of data packets that have a specific format depending on the kind of message. figure 38 host communication in order to transfer data to the isar 34 the host writes messages to the mailbox. in the opposite direction the isar 34 releases an interrupt to the host to indicate that a message can be read from the mailbox.
psb 7115 operational description semiconductor group 61 02.98 3.1.1 message structure this chapter describes the format of the messages that are used to transfer information between host and isar 34. the coding of the individual messages is described in detail in chapter 3.2 pp. depending on the kind of message, the structure and message length may be different. all messages consist of: ? interrupt status byte (his or iis) ? control register msb (ctrl msb) ? control register lsb (ctrl lsb) for some messages a certain number of additional bytes must be written to or read from the mailbox, respectively: ? 1st parameter ? 2nd parameter ?: ? n-th parameter figure 39 message transfer
psb 7115 operational description semiconductor group 62 02.98 3.1.2 interrupt status byte this chapter describes the format of the interrupt status byte which is part of every message transferred between host and isar 34. there are two types of interrupt status bytes depending on the direction of data flow: the interrupt status byte has a structure that defines the type of message, i.e. it contains information to which buffer the message is related to, the kind of message and to which functional block of the isar 34 the message is related to: the coding for the his and iis registers are listed below. it should be noted, that not all code combinations of buffer selection (dps), message coding (msc) and message destination/source (mds) are available at the programming interface. it is also important to note that the coding for test/diagnostics messages (dps = 00) does not conform to the above shown structure of msc and mds. instead these bits fully specify an individual message function. some of the test/diagnostics messages are only used for dsp download and are not valid after regular operation has started (see chapter 3.12 dsp program download). his h ost i nterrupt s tatus host ? isar 34 write to reg. 03h iis i sar 34 i nterrupt s tatus isar 34 ? host read from reg. 04h 76543210 his/iis dps msc mds dps ? datapath selection one of the four data paths (0, 1, 2 or 3) of the isar 34 is selected. msc ? message coding msc defines the type of command (e.g. configuration request, configuration response, status event, control command, ? ) to perform a certain function. mds ? message destination/source selects one of the four functional blocks on the isar 34 (buffer, sart, data pump and iom-2) to which the message is sent (host ? isar 34) or from which a message is originated (isar 34 ? host ).
psb 7115 operational description semiconductor group 63 02.98 host interrupt status byte (his host ? isar 34) the structure for the his byte is shown below. not all combinations of buffer selection, message coding and message destination are available at the programming interface. table 5 his structure - path 1, 2 and 3 7 6543210 datapath selection (dps) 0 1 path 1 1 0 path 2 1 1 path 3 message coding (msc) 100000transmit data with sart control command 0 0 0 1 request for configuration 0 0 1 1 request for status 1 0 0 1 configuration setup 1 0 1 0 control command message destination/source (mds) 0 0 command for buffer 0 1 command for sart 1 0 command for pump 1 1 command for iom-2
psb 7115 operational description semiconductor group 64 02.98 the his structure is different for data path 0 which is used for the monitor channel, general control and test/diangostics functions. . table 6 his structure - path 0 7 6543210 datapath selection (dps) 0 0 path 0 message coding (msc) 001000iom-2 request for configuration 111100buffer configuration setup 111110buffer control command 011101buffer status request 100101timer interrupt on/off 000100request selftest result 000101request for software version number 110001monitor channel configuration setup 010001monitor channel configuration request 110000monitor channel transmit data 101000soft reset 001010gpio data re quest 101010gpio configuration command
psb 7115 operational description semiconductor group 65 02.98 isar 34 interrupt status byte (iis) the structure for the iis byte is shown below. also for iis not all combinations of buffer selection, message coding and message destination are available at the programming interface. one message does not conform to the described structure of dps, msc and mds. it has a general code (iis = 0), which is used for normal operation and not for test/ diagnostics functions. note: all messages which are not listed here or described in the detailed message description (starting with chapter 3.2) must be ingored by the host if released from the isar 34. table 7 iis structure - path 1, 2 and 3 7 6543210 datapath selection (dps) 0 1 path 1 1 0 path 2 1 1 path 3 message coding (msc) 100000receive data with sart status event 1 0 0 1 mailbox contains configuration data 1 0 1 0 mailbox contains status event 1 0 1 1 mailbox contains status information message destination/source (mds) 0 0 indication from buffer 0 1 indication from sart 1 0 indication from pump 1 1 indication from iom-2
psb 7115 operational description semiconductor group 66 02.98 the iis structure is different for data path 0 which is used for the monitor channel, general control and test/diangostics functions. : note: the timer interrupt is not coded as a path 0 message but for data path 1. however, the use of the timer interrupt does not require path 1 operation, it may be used for any purpose. table 8 iis structure - path 0 7 6543210 datapath selection (dps) 0 0 path 0 message coding (msc) 1 0 1 0 0 0 general iom-2 configuration response 111101buffer status response 1 1 1 1 1 0 buffer status event (path 0) 0 0 0 0 0 0 buffer status event - buffer available (path 0, 1, 2 and 3) 1 1 1 1 1 1 invalid message received 100100selftest response 1 0 0 1 0 1 software version number response 1 1 0 0 0 1 monitor channel configuration response 1 1 0 0 0 0 monitor channel receive data 1 1 0 0 1 0 monitor channel status event 1 0 1 0 1 0 gpio status event/response 0 1 1 0 1 0 1 0 timer interrupt event
psb 7115 operational description semiconductor group 67 02.98 3.1.3 control registers and parameters this chapter describes the structure of the remaining elements of a message, which are control registers, parameters and data. the most significant byte of the control register (ctrl msb) contains configuration, status or control information which depends on the type of message. figure 40 control registers and parameters the least significant byte of the control register (ctrl lsb) is used to indicate the total number of bytes transferred via the mailbox (mailbox i/o data). these mailbox data may contain additional configuration, status or control information as well as user data in receive/transmit direction (figure 40) . for some of the messages no additional data is written to/read from the mailbox, in this case the ctrl lsb is set to 0. the structure of the parameters depends on the type of message being transferred and has no fixed format. therefore it is described with each individual message. ctrl msb ctrl lsb 1st parameter 2nd parameter n-th parameter number of parameters n config, status or control information mailbox i/o data mailbox i/o data mailbox i/o data
psb 7115 operational description semiconductor group 68 02.98 3.1.4 configuration after reset the proceeding after hardware reset is shown in figure 41 . this version of the isar 34 requires a download of the dsp program into external memory, future versions will be able to store the dsp program in flash memory and may even provide completely new features. the corresponding dsp program is delivered in a binary file together with the device. when this binary file is downloaded, an automatic test of the chip version number is performed within the download procedure, so the host does not need to evaluate it. after the dsp program download procedures are finished the host checks the global variable status if the download was successful. the isar 34 will also perform an automatic selftest of the chip at the end of the download procedure. the host requests the result of this selftest to ensure that no basic hardware error is given. the software version number can be read to get information on what features are provided with this version of the dsp program. the isar 34 is now ready for configuration of the functional blocks which should be done in the given sequence (buffer, pump, iom-2 and sart) and data transfer can be started.
psb 7115 operational description semiconductor group 69 02.98 figure 41 initialisation procedure to establish a link on a data path, the four functional blocks, buffer, data pump, iom-2 interface and sart must be configured first. since the configuration of the data pump will reset the whole data path except buffer configuration, the pump should be configured right after buffer configuration. it is recommended to follow this configuration sequence to provide for proper operation. reset send command "autostart" download successful (status =0) ? configure data pump configure iom-2 interface configure sart request for isar 34 selftest result normal operation mode initialization complete download complete no yes done isar 34 ready for configuration and data transfer configure buffer isar 34 selftest is performed automatically error detected ? yes no 7115_60.a abort procedure download program to external memory host tries to start the dsp program of the isar 34. abort procedure the parameter status is a global variable of the dsp program download procedures.
psb 7115 operational description semiconductor group 70 02.98 the table below shows the configuration parameters for each of the four blocks and the reference to the corresponding parameter setting. detailed information about the individual parameters is provided with the corresponding configuration setup messages. table 9 configuration parameters functional block configuration parameter parameter setting buffer ? buffer base priority bbp ? maximum message length mml data pump ? pump mode (fax, datamodem, halfduplex modulation, v.110, dtmf, dtmf transmission or bypass) pmod ? originating/answering mode oam ? transmitter output attenuation toa ? calling and answer tones atn, ctn ? echo protector tone ept ? guard tone selection gts ? modulation scheme v34r, v32r, ? ? automode operation amod ? v.8 negotiation v8 ? data rate (v.110) vdr ? flow control (v.110) fct ? rejection level (dtmf) rel iom-2 interface ? iom-2 access enable/disable iom ? time slot position rtso, rcs ttso, tcs ? time slot length tsl ? switching of du/dd lines txd, rxd ? coding (pcm a-law, m -law) cod ? rate conversion rcv
psb 7115 operational description semiconductor group 71 02.98 sart ? sart mode (v.14, hdlc, binary, fsk v.14) smode ? receive/transmit channel disable (halfduplex modulation) hdmc ? hdlc formatting (hdlc regular/inverted, interframe fill, fcs length, enable/disable fcs, data underrun operation) hio iff flen edf, duo ? v.14/fsk v.14 formatting (overspeed range, stop bits, parity bits, character size, buffer flush timeout) ovsp, snp, eop, edp nsb, chs, bft ? binary formatting (data underrun operation, bit swapping, data underrun fillword) duo, bsw, dufw table 9 configuration parameters functional block configuration parameter parameter setting
psb 7115 operational description semiconductor group 72 02.98 3.1.5 message transfer from host to isar 34 the procedure to write a message to the isar 34 mailbox is shown in figure 42 . the mechanism to access the isar 34 mailbox is the same for all messages, which are: ? configuration setup ? configuration request ? status request ? control commands ? control commands along with transmit data figure 42 write message transfer when a message is written to the mailbox, the isar 34 will transfer the whole message to the destination buffer which is indicated in the host interrupt status byte (his). during that time another message must not be entered by the host, however due to the mailbox structure, the message transfer is performed rather fast and will not delay any host access. write message to isar 34 mailbox read hia-bit mailbox access permitted (hia=0) ? write to ctrl msb write to ctrl lsb (= number n of parameters ) no yes write parameter to mailbox another parameter necessary (n>0) ? write host interrupt status byte to his-regsiter no yes done n := n - 1 indicates the new message in the mailbox to the isar 34 reset write address register to 0 7115_60.a
psb 7115 operational description semiconductor group 73 02.98 therefore, before any access to the mailbox is done, the host should read the host interrupt acknowledge bit (hia), to verify that the registers are available again (hia = 0) and a new message may be written to the mailbox. the control registers (ctrl msb and lsb) should be written first, where the ctrl lsb contains the total number of bytes which will be entered to the mailbox. before any data is written to the mailbox (address 02h), the write pointer (address 01h) must be reset to 0. after a byte is written to the mailbox, the write address pointer is autoincremented and doesn't need to be reprogrammed. this allows for fast access to the mailbox. if there are successive messages with the same mailbox contents, the mailbox data does not need to be written again, as this data is still available in the mailbox memory from the previous message. it allows the host to flexibly reprogram the write pointer and its respective memory location only for those mailbox contents which are different from the previous message. important note: it is important to note that the his byte must be entered as the very last byte of the message as this will indicate the new register and mailbox contents to the isar 34. an access to the his register will terminate the message transfer and automatically set the hia bit which is reset again by the isar 34 as soon as new data can be entered to the mailbox.
psb 7115 operational description semiconductor group 74 02.98 3.1.6 message transfer from isar 34 to host the procedure to read a message from the isar 34 mailbox is shown in figure 43 . the mechanism to access the isar 34 mailbox is the same for all messages, which are: ? configuration response (initiated by configuration request message) ? status response (initiated by status request message) ? status events ? status events along with receive data figure 43 read message transfer if the isar 34 has a message available in the mailbox to be read by the host, it will activate the int-line, provided the interrupt is not masked (msk bit). to ensure the interrupt line is activated by the isar 34 and not from a different interrupt source in the system (e.g. from the transceiver device), the interrupt status bit sta should be checked. for the message transfer the isar 34 interrupt status register (iis) should be read first. it defines the type of message and indicates the source where the message was initiated. read message from isar 34 mailbox int received from isar 34 done read iis register read isar 34 ctrl msb read isar 34 ctrl - lsb (= number n of bytes in the mailbox) another byte to be read from the mailbox (n>0) ? no yes read one byte from the mailbox release mailbox for next data transfer ( set iia=0 ) n := n - 1 indicates to the isar 34 that the whole message has been read from the mailbox reset read address register to 0 check sta bit 7115_60.a
psb 7115 operational description semiconductor group 75 02.98 then the ctrl msb and lsb are read by the host, where the lsb indicates the total number of bytes which are available in the mailbox . before data is read from the mailbox (address 02h), the read pointer (address 00h) must be reset to 0 to read the data starting with the first byte in sequence. for each read access to the mailbox the read address pointer is autoincremented and does not need to be reprogrammed by the host. this allows for fast access to the mailbox. important note: it is important to note that the iia bit must be reset as the very last register access of the message, as this will indicate to the isar 34 that the message has been completely read. the mailbox is released and may be filled with new contents. it is not necessary to read the mailbox if its content is not required by the host, e.g. if data is not valid. the host can discard the contents by just writing the iia bit as this will release the whole mailbox. a response message is always initiated by the host releasing a request message to the isar 34 (see figure 44 ). the other messages are initiated by the state machine residing on the host side (messages from host to isar 34) or residing on the isar 34 (messages from isar 34 to host). figure 44 message directions the isar 34 releases an interrupt request to the host to indicate that a message must be read from the mailbox. the host can mask the interrupt source (bit msk = 0) to avoid any interrupt state being indicated to the host by activating the int-line. however, the mask bit affects only the generation of the interrupt, but not the interrupt status from being set (sta bit) which can be polled by the host. 7115_ 3 configuration setup configuration request configuration response status request status response control command control command along with transmit data status event status event along with receive data isar 34 psb 7115 host
psb 7115 operational description semiconductor group 76 02.98 3.1.7 message overview the data path for the b-channel consists of fifo buffer, sart, data pump and iom-2 interface. transmit/receive data and configuration, status and control information is exchanged between the host and the isar 34 by a set of messages. buffer configuration ? configuration setup host t isar 34 the host sets the priority at which each buffer's request will be serviced by the host and the message length at which data will be transferred between the host and the mailbox. ? configuration request host t isar 34 the host can request the current configuration, i.e. parameter settings such as base priority and message length. ? configuration response host isar 34 after a configuration request by the host, the isar 34 will respond with the current parameter settings. ? control command host t isar 34 the host sends control commands to the isar 34 in order to clear or reset buffers. buffer status ? status request host t isar 34 the host can request the current status of the buffers, i.e. number of messages and free locations in the buffers. two different types of status responses can be requested. ? status response host isar 34 after a status request by the host, the isar 34 will respond with the current status information. ? status events host isar 34 during data transfer the isar 34 indicates to the host, whether the buffer is able to store another message, i.e. if new data can be entered.
psb 7115 operational description semiconductor group 77 02.98 sart configuration ? configuration setup host t isar 34 the host configures the mode (binary, hdlc, async) for the sart and sets further parameters depending on the mode. sart data ? status events with receive data host isar 34 during data reception the isar 34 indicates to the host, when error conditions or mode specific events occur, e.g. when the end of an hdlc frame was detected. ? control commands with transmit data host t isar 34 during data transmission the host controls mode specific functions e.g. the hdlc framing (frame start, frame end) and the generation of break signals in async mode. pump configuration ? configuration setup host t isar 34 the host configures the mode (fax modulations, datamodem modulations, halfduplex modulations, v.110, dtmf, dtmf transmission or by pass) for the data pump and sets further parameters depending on the mode. ? control commands host t isar 34 the host sends control commands to the isar 34 in order to enable/disable the pump and to set mode specific control commands (e.g. dtmf tones to be generated). pump status ? status request host t isar 34 the host can request the current configuration of the data pump (pump mode, originating/answering mode). ? status response host isar 34 after a configuration request by the host, the isar 34 will respond with the current parameter settings. ? status events host isar 34 the isar 34 indicates to the host mode specific events that occur during data transfer, such as dtmf tones received or control bit change in v.110.
psb 7115 operational description semiconductor group 78 02.98 important note: in future versions of the isar 34 the message length for response messages can be different from this version 2.1, i.e. new parameters may additionally be provided which is indicated by an increased parameter nom (= number of valid bytes in the mailbox). if the isar 34 in this version provides more parameters than specified herein, the host should ignore all mailbox data that exceeds the message length determined by nom as specified. iom-2 configuration ? configuration setup host t isar 34 the host configures the length and position of the iom-2 timeslots. ? configuration request host t isar 34 the host can request the current iom-2 configuration, i.e. the current settings of timeslot-length and position. ? configuration response host isar 34 after a configuration request by the host, the isar 34 will respond with the current configuration setting. ? control commands host t isar 34 the host sends control commands to the isar 34 for iom-2 control during normal operation. gpio configuration ? configuration setup host t isar 34 the host configures status, direction, interrupts etc. of the gpio pins. gpio status ? status request host t isar 34 the host requests the current status of the gpio pins. ? status event/response host isar 34 after a state change on a gpio with unmasked interrupt, this status event reports the current gpio status to the host. the same message is used as a status response after a status request from the host.
psb 7115 operational description semiconductor group 79 02.98 3.2 buffer configuration 3.2.1 buffer configuration setup (host ? isar 34) : 76543210 dps msc mds his 0 0 15 14 13 12 11 10 9 8 ctrl msb 00000 bbp 76543210 ctrl lsb 1 76543210 1. parameter mml dps ? datapath selection 00: path 0 01: path 1 10: path 2 11: path 3 msc ? message coding the message coding is different for datapath 0 and datapath 1, 2, 3. 1111: configuration setup for data path 0 (dps = 00) 1001: configuration setup for data path 1, 2 or 3 (dps = 01, 10, 11) bbp ? buffer base priority 000: priority is not changed by the configuration command 001: change base priority to 1 (lowest priority) : : 111: change base priority to 7 (highest priority) reset value: bbp = 4 datapaths 1, 2 and 3 (dps = 01, 10, 11) bbp = 5 datapath 0 (dps = 00)
psb 7115 operational description semiconductor group 80 02.98 the buffer priority determines the sequence of service if more than one read buffer request for mailbox service at the same time. in such a case the buffer with highest priority is served first and the priority of all pending buffers is increased by one. after being served, the priority of the serviced buffer is reset to its base value, which is selected by the above given configuration command. so a buffer with a higher base priority will be served more often than a buffer with a lower base priority, moreover, the higher the difference of two priority values the more often the one buffer will be serviced first. if the additional value (maximum message length) is omitted (ctrl lsb = 0), only the base priority is changed. in this way the buffer base priority can be reconfigured to a different value during normal operation without any loss of data consistency. by changing the base priority, the current priority is reset to the new base value. for highest throughput and best internal performance it is recommended to use the highest value for mml. mml ? maximum message length the maximum message length defines the block size of data that is transferred via the mailbox. a data block that is read from or written to the mailbox has a block size less or equal the maximum message length mml. the maximum value for mml is limited by the fifo size (mpl = maximum possible message length) for the respective datapath. mpl can be read by a buffer configuration request message (see next chapter). the fifo size depends on the memory configuration of the isar 34. ? with external sram 128kx16, 15ns: mpl mml (reset value) path 0 61 32 path 1 253 32 path 2 253 32 path 3 253 32
psb 7115 operational description semiconductor group 81 02.98 3.2.2 buffer configuration request (host ? isar 34) the current buffer configuration can be requested by the host. the request is fully specified by the host interrupt status register (his), i.e. the mailbox control registers are set to 0 and no parameters are required. : 76543210 dps msc mds his 0 0 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 0 dps ? datapath selection 00: path 0 01: path 1 10: path 2 11: path 3 msc ? message coding the message coding is different for datapath 0 and datapath 1, 2, 3. 0111: configuration request for datapath 0 (dps = 00) 0001: configuration request for datapath 1, 2 or 3 (dps = 01, 10, 11)
psb 7115 operational description semiconductor group 82 02.98 3.2.3 buffer configuration response (isar 34 ? host) the isar 34 provides the configuration data, which was requested by the host, via the mailbox. the coding is similar to the configuration setup. 76543210 dps msc mds iis 0 0 15 14 13 12 11 10 9 8 ctrl msb CCCCC bbp 76543210 ctrl lsb 2 76543210 1. parameter mml 76543210 2. parameter mpl dsp ? datapath selection 00: path 0 01: path 1 10: path 2 11: path 3 msc ? message coding the message coding is different for datapath 0 and datapath 1, 2, 3. 1111: configuration response from datapath 0 (dps = 00) 1001: configuration response from datapath 1, 2 or 3 (dps = 01, 10 or 11) bbp ? current buffer base priority 000: not used 001: base priority of 1 (lowest priority) : : 111: base priority of 7 (highest priority)
psb 7115 operational description semiconductor group 83 02.98 in receive direction the isar 34 gathers all received data words from the sart up to the selected message length, before the message is passed to the mailbox. messages of reduced length may be passed on certain events such like error conditions or hdlc frame end (see chapter 3.5.1 sart status events with receive data). in transmit direction it's the responsibility of the host that transmit messages do not exceed the selected message length, to avoid a buffer overflow and loss of data. it must be ensured that mml does not exceed mpl in the configuration setup message (see chapter 3.2.1 ). therefore it is recommended to issue a buffer configuration request message to verify the currently selected (mml) and the maximum possible message length (mpl). moreover, this enables the software to automatically adapt to the hardware platform, as the isar 34 may provide different fifo buffer sizes depending on the memory configuration in future versions. mml ? currently selected maximum message length mml contains the maximum message length that has been configured by the host. if this value has not been programmed by the host, mml contains the reset value for the maximum possible message length (see below). mpl ? maximum possible message length mpl contains the maximum possible message length that can be configured. the value for mpl depends on the memory configuration of the isar 34. ? with external sram 128kx16, 15ns: mpl mml (reset value) path 0 61 32 path 1 253 32 path 2 253 32 path 3 253 32
psb 7115 operational description semiconductor group 84 02.98 3.2.4 buffer control command (host ? isar 34) the i/o-buffer control commands are interpreted immediately after being received by the isar 34. the buffer clear commands do not change the settings of the base priority or the message length. the reset command clears both, read and write buffers, and reset them to their initial factory settings. 76543210 dps msc mds his 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 0 0 crb 76543210 ctrl lsb 0 dps ? datapath selection 00: path 0 01: path 1 10: path 2 11: path 3 msc ? message coding the message coding is different for datapath 0 and datapath 1, 2, 3. 1111: control command for datapath 0 (dps = 00) 1010: control command for datapath 1, 2 or 3 (dps = 01, 10 or 11) mds ? message destination/source the destination coding is different for datapath 0 and datapath 1, 2, 3. 10: message is addressed to buffer (for dps = 00) 00: message is addressed to buffer (for dps = 01, 10 or 11) crb ? clear / reset buffers 00: clear receive buffer 01: clear transmit buffer 10: reset read and write buffers to their initial values
psb 7115 operational description semiconductor group 85 02.98 3.3 buffer status 3.3.1 buffer status request (host ? isar 34) the request is fully specified by the host interrupt status register (his) and the mailbox control registers, i.e. additional parameters are not used. the i/o-buffer status request is serviced immediately after being received by the isar 34. 76543210 dps msc mds his 15 14 13 12 11 10 9 8 ctrl msb 0000000sts 76543210 ctrl lsb 0 dps ? datapath selection 00: path 0 01: path 1 10: path 2 11: path 3 msc ? message coding the message coding is different for datapath 0 and datapath 1, 2, 3. 0111: status request for datapath 0 (dps = 00) 0011: status request for datapath 1, 2 or 3 (dps = 01, 10 or 11) mds ? message destination/source the destination coding is different for datapath 0 and datapath 1, 2, 3. 01: message is addressed to buffer (for dps = 00) 00: message is addressed to buffer (for dps = 01, 10 or 11) sts ? status type select the status request will cause the generation of ? 0: ? a status response with additional information about the buffers 1: a buffer available indication
psb 7115 operational description semiconductor group 86 02.98 the status response with additional information about messages and free locations in the receive and transmit buffers is described in chapter 3.3.2 . the second option allows the host to force the generation of a buffer available indication as specified in chapter 3.3.3 . however there is a slight difference in the functionality of the resulting indication message: a buffer available indication that is initiated by the isar 34, only contains information about those buffers where a transition from not enough free space to enough free space for another message occurs. all buffers that are not serviced by that time, will not be indicated in a following buffer available indication that results from the status transition of a different buffer. however, a status request with sts = 1 forces the isar 34 to generate a buffer available indication for the transmit buffer of the selected datapath (specified in the his register), even if there is no state transition for that buffer. this command is useful to force a first data request message from the isar 34 after a datapath is fully configured, although the first request message is automatically generated after sart configuration.
psb 7115 operational description semiconductor group 87 02.98 3.3.2 buffer status response (isar 34 ? host) the isar 34 returns status information about the buffers if requested by the host (see chapter 3.3.1 ). 76543210 dps msc mds iis 15 14 13 12 11 10 9 8 ctrl msb C C C C rdm3 rdm2 rdm1 rdm0 76543210 ctrl lsb 6 76543210 1. parameter nbrl 76543210 2. parameter nbrm 76543210 3. parameter nmr 76543210 4. parameter nbtl 76543210 5. parameter nbtm 76543210 6. parameter nmt dps ? datapath selection 00: path 0 01: path 1 10: path 2 11: path 3
psb 7115 operational description semiconductor group 88 02.98 the control register contains additional information about all buffers that currently have buffer space available for a new message. the information is similar as provided in the general status event message which is a kind of indication for buffer available (see chapter 3.3.3.2 ). however, here the current status of all buffers is indicated regardless whether there is a state transition in the individual buffer. detailed information about free locations in receive and transmit buffers and about the number of messages currently stored in the buffers are available from the mailbox. these parameters only refer to the buffer which is associated to the selected data path in iis register. comment as the his register and the control word are internally also written to the buffers a message of length n will always require (n+3) buffer locations. msc ? message coding the message coding is different for datapath 0 and datapath 1, 2, 3. 1111: status response from datapath 0 (dps = 00) 1011: status response from datapath 1, 2 or 3 (dps = 01, 10 or 11) mds ? message destination/source the source coding is different for datapath 0 and datapath 1, 2, 3. 01: message is originated from the buffer (for dps = 00) 00: message is originated from the buffer (for dps = 01, 10 or 11) rdm3 - 0 ... request for next data message from channel 3, 2, 1 or 0 if rdm0, rdm1, rdm2 or rdm3 is set, the corresponding channel 0, 1, 2 or 3 requests for a new data message from the host, i.e. there is enough free buffer space for another message. nbrl ? number of free bytes in the receive buffer - lsb nbrm ? number of free bytes in the receive buffer - msb nmr ? number of messages in the receive buffer nbtl ? number of free bytes in the transmit buffer - lsb nbtm ? number of free bytes in the transmit buffer - msb nmt ? number of messages in the transmit buffer
psb 7115 operational description semiconductor group 89 02.98 3.3.3 buffer status event (isar 34 ? host) there are two message types for status events from the buffer: ? status event that is related to a certain buffer (see chapter 3.3.3.1 ) ? indication for buffer available - general code for all buffers (see chapter 3.3.3.2 ) 3.3.3.1 buffer specific status event (isar 34 ? host) : 76543210 dps msc mds iis 15 14 13 12 11 10 9 8 ctrl msb stev 76543210 ctrl lsb 0 dps ? datapath selection 00: path 0 01: path 1 10: path 2 11: path 3 msc ? message coding the message coding is different for datapath 0 and datapath 1, 2, 3. 1111: status event from datapath 0 (dps = 00) 1010: status event from datapath 1, 2 or 3 (dps = 01, 10 or 11) mds ? message destination/source the source coding is different for datapath 0 and datapath 1, 2, 3. 10: message is originated from the buffer (for dps = 00) 00: message is originated from the buffer (for dps = 01, 10 or 11) stev ? status event code 1fh: transmit buffer overflow 2fh: receive buffer overflow
psb 7115 operational description semiconductor group 90 02.98 3.3.3.2 buffer general status event (isar 34 ? host) if a data path is online and the associated write buffer has space available for a new message, the status event message buffer available is generated to request new data from the host. the i/o-buffer control unit generates write buffer status event messages that cover information about all buffers, thus the iis register contains a general code (iis = 0). in this way the load for transfering messages is decreased significantly, as a single message may request data for more than one datapath. it is the responsibility of the host to dispatch rdmx to the controller routines of the relevant datapath. a status event is generated by the control unit and indicated to the host when ? at least one of the write buffers changes its state from not enough free space to enough free space for another data message, or when ? at least one of the write buffers has still enough free space for another message immediately after a new message was written into this buffer. only when either of these two states is met, the status event message is generated. if the request is not serviced by the host, the isar 34 will not generate a new status event message to request data for that path. it should be noticed that the corresponding bit for that buffer remains not set in the control register each time another buffer generates an interrupt to request new data. however a status request message (see chapter 3.3.1 ) can force the generation of an indication for buffer available for a certain buffer. 76543210 dps msc mds iis 00000000 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 rdm3 rdm2 rdm1 rdm0 76543210 ctrl lsb 0 rdm3 - 0 ... request for next data message from channel 3, 2, 1 or 0 if bit rdm3, rdm2, rdm1 or rdm0 is set, the corresponding datapath 0, 1, 2 or 3 requests for a new data message from the host.
psb 7115 operational description semiconductor group 91 02.98 the general proceeding for data transfer from the host to the transmit buffer would be: ? after reset and completion of the initialization procedure the isar 34 will release an initial status event message with rdm0 = rdm1 = rdm2 = rdm3 = 1 ? the host configures buffer, data pump, iom-2 interface and sart ? the host writes the first message to the buffer (buffer is empty after reset) ? if the remaining buffer space is greater than the programmed message length, there will be an immediate interrupt to the host, who in turn can transfer the next message. ? if the remaining buffer space is smaller than the programmed message length, there will be no interrupt to the host until data is transmitted from the buffer and enough space is available to accept one complete message. ? if there is a request for message to the host and the host has no new message to send, the host should store the request information, so for new data it can immediately continue with transfering it to the buffer. ? the host can force the generation of an indication for buffer available for a certain buffer (see chapter 3.3.1 ).
psb 7115 operational description semiconductor group 92 02.98 3.4 sart configuration for the b-channel datapaths (path 1 and 2) the configuration setup message requires a specific coding depending on the required sart mode (hdlc, async or binary). the coding for each mode is described in the following chapters. the d-channel datapath (path 3) is always operating in hdlc mode, therefore no sart configuration setup is required. as datapath 0 is used for the monitor channel and for test/diagnostics functions, there is no sart function and no sart messages are defined. for sart configuration all parameters have to be set for the corresponding sart mode even though a single parameter may not be different from a previous setting. important note: after configuration of the pump, the configuration information of the sart gets lost, therefore the sart unit must be configured after the pump configuration. 3.4.1 sart configuration setup - hdlc (host ? isar 34) 76543210 dps msc mds his 100101 15 14 13 12 11 10 9 8 ctrl msb hdmc 0 0 smode 76543210 ctrl lsb 1 76543210 1. parameter 0 0 0 hio iff flen edf duo dps ? datapath selection 01: path 1 10: path 2
psb 7115 operational description semiconductor group 93 02.98 hdmc ? halfduplex mode configuration 00: receive and transmit channel are enabled (default) 01: receive channel is disabled 10: transmit channel is disabled 11: not used in halfduplex mode the pump would transfer idle bits in the direction that is currently not in use, so the corresponding receive or transmit channel can be selectively disabled to reduce the interrupt load for not valid data. for all other pump modes except halfduplex mode, hdmc must be set to its default value 00. smode ? sart mode 0000: disable sart 0010: v.14 mode 0011: hdlc mode 0100: binary mode 0101: fsk v.14 mode all other codes reserved hio ? hdlc input/output 0: regular 1: inverted inverted describes a mode where all bits are changed from 0 to 1 and from 1 to 0 after hdlc formatting. iff ? interframe fill 0: flags 1: 1 flen ? fcs length 0: 16 bit fcs 1: 32 bit fcs (not supported in isar 34 v2.1) edf ? enable/disable fcs 0: enable fcs (regular hdlc operation) 1: disable fcs this refers to fcs generation in transmit direction and fcs checking in receive direction. duo ? data underrun operation for data underrun in tx direction ? 0: ? abort is generated (default) 1: ? frame end (fcs and final flag) is generated
psb 7115 operational description semiconductor group 94 02.98 3.4.2 sart configuration setup - async (host ? isar 34) async denotes an asynchronous formatting of data according to itu-t v.14. two separate modes are distinguished for async which depends on the selected modulation scheme at the data pump. 76543210 dps msc mds his 100101 15 14 13 12 11 10 9 8 ctrl msb hdmc 0 0 smode 76543210 ctrl lsb 2 76543210 1. parameter 0 ovsp snp psl edp nsb chs 76543210 2. parameter bft dps ? datapath selection 01: path 1 10: path 2 hdmc ? halfduplex mode configuration 00: receive and transmit channels are enabled (default) 01: receive channel is disabled 10: transmit channel is disabled 11: not used in halfduplex mode the pump would transfer idle bits in the direction that is currently not in use, so the corresponding receive or transmit channel can be selectively disabled to reduce the interrupt load for not valid data. for all other pump modes except halfduplex mode, hdmc must be set to its default value 00.
psb 7115 operational description semiconductor group 95 02.98 smode ? sart mode 0000: disable sart 0010: v.14 mode (used for pump modes v.110, v.32, v.32bis, v.22, v.22bis) 0011: hdlc mode 0100: binary mode 0101: fsk v.14 mode (used for pump modes v.21, v.23, bell 103, bell 202) all other codes reserved. there is a difference in the pump modes fsk v.14 and v.14: ? for fsk v.14 the bit alignment during an idle sequence gets lost, since there is only one frequency for the mark bit and so there's no fixed baud rate at the data pump during the idle sequence. ? for v.14 mode there is a data stream that has a fixed bit alignment, since the modulation scheme provides a fixed baud rate even during an idle sequence. important note: fsk v.14 mode must not be used for any other pump modes than v.21, v.23, bell 103 and bell 202. ovsp ? overspeed range (valid only for transmit direction) number of stop bits to be deleted 0: 1 of 8 1: 1 of 4 stop bit deletion during data transmission is initiated by a control command, otherwise all stopbits are generated independent of ovsp setting. it is only valid for v.14 mode and not supported for fsk v.14. overspeed range for the transmitter is an option that can be used to increase the data rate in async mode by means of the overspeed mechanism that is actually defined for compensating different data rates due to missing synchronism between an aysnc-receiver and transmitter. snp ? stick/normal parity 0: normal parity 1: stick parity
psb 7115 operational description semiconductor group 96 02.98 the buffer flush counter determines the length of a timer that is started when after a single character an idle sequence is being received. this is to ensure, that async characters are indicated and transferred to the host in case of a long idle sequence even though the message length is not yet complete. if the timeout is disabled, the last datawords remain in the receiver buffer - even during a long idle sequence - until the message length is complete which is then indicated to the host. for fast data rates a value in the range bft = 10 ? 50 is suitable, whereas for slow data rates (v.21/300 bit/s) a lower value is recommended. the bft-value should be selected high enough to avoid a too early buffer flush, which would increase the mailbox load. the symbolrate refers to the selected modulation scheme which is selected for pump configuration. psl ? parity select the selection (even, odd, stick 0, stick 1) depends on the setting of snp: snp = 0 snp = 1 0: odd parity 0: parity bit = 1 1: even parity 1: parity bit = 0 edp ? enable/disable parity bit 0: disable parity 1: enable parity nsb ? number of stop bits 0: 1 stop bit 1: 2 stop bits chs ? character size 00: 5 bit 01: 6 bit 10: 7 bit 11: 8 bit bft ? buffer flush timeout (valid for receive direction only) 0: flush timeout disabled 1: flush timeout = 2 symbolrate 2: = 4 symbolrate :: :: 254: = 508 symbolrate 255: = 510 symbolrate
psb 7115 operational description semiconductor group 97 02.98 3.4.3 sart configuration setup - binary (host ? isar 34) 76543210 dps msc mds his 100101 15 14 13 12 11 10 9 8 ctrl msb hdmc 0 0 smode 76543210 ctrl lsb 2 76543210 1. parameter 0 0 0 0 0 0 duo bsw 76543210 2. parameter dufw dps ? datapath selection 01: path 1 10: path 2 hdmc ? halfduplex mode configuration 00: receive and transmit channel are enabled (default) 01: receive channel is disabled 10: transmit channel is disabled 11: not used in halfduplex mode the pump would transfer idle bits in the direction that is currently not in use, so the corresponding receive or transmit channel can be selectively disabled to reduce the interrupt load for not valid data. for all other pump modes except halfduplex mode, hdmc must be set to its default value 00. smode ? sart mode 0000: disable sart 0010: v.14 mode 0011: hdlc mode 0100: binary mode 0101: fsk v.14 mode all other codes reserved
psb 7115 operational description semiconductor group 98 02.98 duo ? data underrun operation for data underrun in tx direction ? 0: ? previous databyte in tx buffer is continuously transmitted 1: ? fillword in mailbox (2nd parameter) is continuously transmitted the fillword functionality can be used to transmit 1 or 0 or any other 8 bit value without continuous message transfer between host and isar 34. bsw ? bit swapping 0: lsb is transmitted/received first 1: msb is transmitted/received first dufw ? data underrun fill word this fillword is transmitted continuously if a data underrun condition occurs in transmit direction. this functionality is only valid if the duo bit in the first parameter is set.
psb 7115 operational description semiconductor group 99 02.98 3.4.4 sart configuration setup - disable sart (host ? isar 34) if the sart is disabled, the data received by the pump is not forwarded to the receive buffer. in transmit direction, a continuous sequence of 1 (marks) are forwarded to the pump if the sart is disabled. 76543210 dps msc mds his 100101 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 0 smode 76543210 ctrl lsb 0 dps ? datapath selection 01: path 1 10: path 2 smode ? sart mode 0000: disable sart 0010: v.14 mode 0011: hdlc mode 0100: binary mode 0101: fsk v.14 mode all other codes reserved
psb 7115 operational description semiconductor group 100 02.98 3.5 sart data data together with status information or control commands is exchanged by 2 types of operation, which are described in the following two chapters. the parameter mds = 00 indicates that the message is related to the buffer as the user data is transferred to and from the buffers. however, the whole message is described as a sart message, since status information, originated from the sart control unit and control information which is meant for the sart unit is transferred along with it. 3.5.1 sart status events with receive data (isar 34 ? host) the sart receiver status, which is always data related, is passed to the host along with any data transfer via the mailbox. the sart status is coded in the ctrl msb, while the ctrl lsb indicates the number of data available in the mailbox . certain sart receive state changes cause an immediate buffer flush event to the associated interface buffer, i.e. any time when such a state changes, all data in the internal fifo buffer is transferred to the host even if the buffer was not yet filled up to the programmed message length. most status bits are related to the last databyte of the mailbox (e.g. parity error). others, like frame start in hdlc mode are related to the first databyte in the mailbox. if no bit is set, messages of the predefined length are transferred.
psb 7115 operational description semiconductor group 101 02.98 3.5.1.1 sart status events with receive data - hdlc (isar 34 ? host) 76543210 dps msc mds iis 100000 : : 15 14 13 12 11 10 9 8 ctrl msb C fed fsd fad rer cer C nmd : : 76543210 ctrl lsb nom : : 76543210 1. parameter 1st databyte of the message : : 76543210 n. parameter n-th databyte of the message dps ? datapath selection 01: path 1 10: path 2 11: path 3 a status information is valid, if the corresponding bit is set to 1: fed ? frame end detected fsd ? frame start detected fad ? frame abort detected rer ? residue error detected received data is not multiple of 8 bits. cer ? crc error detected mailbox contains all received data. nmd ? no more data (only valid with fax modulations pump mode) nmd indicates that the carrier of the remote fax modem is no longer available. nom ? number of valid bytes in the mailbox indicates the number n of valid data bytes to be read from the mailbox.
psb 7115 operational description semiconductor group 102 02.98 for the frame end-condition, the fcs is contained in the hdlc frame as the last 2 octetts of the message (16 bit fcs). for all conditions indicated in bit 14 - bit 10 (ctrl msb), valid data in the buffer is indicated to the host although the message length may not yet be complete. for short frames where the frame length does not exceed the maximum message length (mml), fed and fsd can be set within one message. incomplete hdlc frames indicated in bit 12 - 10 are available in the mailbox including the erroneous data word. however, the host does not need to read such a frame from the buffer, it can skip this frame by only setting the isar 34 interrupt acknowledge bit (iia).
psb 7115 operational description semiconductor group 103 02.98 3.5.1.2 sart status events with receive data - async (isar 34 ? host) break end occurs with the first character in the mailbox, which is not valid. if the message contains more than one character, all characters starting from the second are valid. all other status indications (bit 12 - 10) refer to the last character of the message, so the last character is not valid if one of these bits is set. 76543210 dps msc mds iis 100000 15 14 13 12 11 10 9 8 ctrl msb C C bre brs dsd per C C 76543210 ctrl lsb nom 76543210 1. parameter 1st databyte of the message 76543210 n. parameter n-th databyte of the message dps ? datapath selection 01: path 1 10: path 2 note: async mode is not defined for path 3. a status information is valid, if the corresponding bit is set to 1: bre ? break signal end detected brs ? break signal start detected dsd ? deleted stopbit detected it is up to the host to decide whether this indicates a frame error or an allowed stop bit deletion due to overspeed range. per ? parity error nom ? number of valid bytes in the mailbox indicates the number n of valid data bytes to be read from the mailbox.
psb 7115 operational description semiconductor group 104 02.98 for all conditions indicated in bit 12 to 10, valid data in the buffer is indicated to the host although the message length may not yet be complete. for characters with a length of 5, 6 or 7 bits the parity bit is transferred together with the character in bit position 5, 6 or 7 respectively (asuming that the first bit is in position 0). it is not available for 8 bit characters. 3.5.1.3 sart status events with receive data - binary (isar 34 ? host) 76543210 dps msc mds iis 100000 15 14 13 12 11 10 9 8 ctrl msb CCCCCCCnmd 76543210 ctrl lsb nom 76543210 1. parameter 1st databyte of the message 76543210 n. parameter n-th databyte of the message dps ? datapath selection 01: path 1 10: path 2 note: binary mode is not defined for path 3. nmd ? no more data (only valid with fax modulations pump mode) nmd = 1 indicates that the carrier of the remote fax modem is no longer available. nom ? number of valid bytes in the mailbox indicates the number n of valid data bytes to be read from the mailbox.
psb 7115 operational description semiconductor group 105 02.98 3.5.2 sart control commands with transmit data (host ? isar 34) the sart transmitter control commands, which are data related, are passed to the isar 34 along with any data transfer via the mailbox. the sart control command is coded in the ctrl msb, while the ctrl lsb indicates the number of data available in the mailbox for transmission. messages without data bytes, i.e. messages with ctrl lsb = 0, must not be sent to the isar 34. 3.5.2.1 sart control commands with transmit data - hdlc (host ? isar 34) 76543210 dps msc mds his 100000 15 14 13 12 11 10 9 8 ctrl msb 0 fed fst gfa 0 0 0 nmd 76543210 ctrl lsb nom 76543210 1. parameter 1st databyte of the message 76543210 n. parameter n-th databyte of the message dps ? datapath selection 01: path 1 10: path 2 11: path 3 the control command is valid if the corresponding bit is set to 1: fed ? frame end the last databyte in the mailbox is indicated as the last of the hdlc frame.
psb 7115 operational description semiconductor group 106 02.98 for datapath 3 an abort will be gnerated automatically by the isar 34 when a data underrun occurs, i.e. the host has failed to write further d-channel data to the mailbox. fst ? frame start the first databyte in the mailbox is indicated as the first of the hdlc frame. gfa ? generate frame abort initiates the generation of an abort sequence. nmd ? no more data (only for fax modulations pump mode) indicates the end of the data stream and initiates the termination of the current modulation. nmd has the similar effect as the command cmd_escape, the difference is, that nmd will cause the fax pump to turn off the modulation right after the last valid data and so enable to cope with timings related to certain protocols. nmd must not be set, if there is another hdlc frame to be sent right after the current fed, as this would cause the flag sequence to be turned off. after the last message of an hdlc frame has been sent (with fed set), immediately another separate message with nmd must be issued by the host, containing one dummy databyte (ctrl lsb = 1), that will be discarded by the isar 34. note: nmd is not defined for path 2 and 3. nom ? number of valid bytes in the mailbox indicates the number n of valid data bytes in the mailbox to be transmitted.
psb 7115 operational description semiconductor group 107 02.98 3.5.2.2 sart control commands with transmit data - async (host ? isar 34) with sab a sequence of at least 2m+3 start bits is initiated and sob enables the host to generate a variable sequence length. if both, sab and sob are set within one message, a break signal of exactly 2m+3 start bits is generated. if dsb is set, every 4th or 8th stopbit is omitted as configured in the sart configuration setup (see chapter 3.4.2 ). setting of v42 causes the generation of 12 stopbits between each character in the mailbox. 76543210 dps msc mds his 100000 15 14 13 12 11 10 9 8 ctrl msb 0 0 sob sab dsb v42 0 0 76543210 ctrl lsb nom 76543210 1. parameter 1st databyte of the message 76543210 n. parameter n-th databyte of the message dps ? datapath selection 01: path 1 10: path 2 note: async mode is not defined for path 3. the individual control function is valid if the corresponding bit is set to 1: sob ? stop break signal sab ? start break signal dsb ? delete stopbits v42 ? generate v42 detect sequence nom ? number of valid bytes in the mailbox. indicates the number n of valid data bytes in the mailbox to be transmitted.
psb 7115 operational description semiconductor group 108 02.98 bit alignment each of the data bytes written to the mailbox contains one v.14 character with the configured number of data bits. the character is aligned to the lsb position and the unused bit positions must be set to 0 by the host software. the lsb (bit d0) is transmitted first in the data stream. 76543210 5 bit length 0 0 0 d4 d3 d2 d1 d0 6 bit length 0 0 d5 d4 d3 d2 d1 d0 7 bit length 0 d6d5d4d3d2d1d0 8 bit length d7 d6 d5 d4 d3 d2 d1 d0
psb 7115 operational description semiconductor group 109 02.98 3.5.2.3 sart control commands with transmit data - binary (host ? isar 34) .. 76543210 dps msc mds his 100000 15 14 13 12 11 10 9 8 ctrl msb 0000000nmd 76543210 ctrl lsb nom 76543210 1. parameter 1st databyte of the message 76543210 n. parameter n-th databyte of the message dps ? datapath selection 01: path 1 10: path 2 note: binary mode is not defined for path 3. the control function is valid if the corresponding bit is set to 1: nmd ? no more data (only for fax modulations pump mode) indicates the end of the data stream and initiates the termination of the current modulation. nmd has the similar effect as the command cmd_escape, the difference is, that nmd will cause the fax pump to turn off the modulation right after the last valid data and so enable to cope with timings related to certain protocols. after the last message of a binary data stream has been sent, immediately another separate message with nmd must be issued by the host, containing one dummy databyte (ctrl lsb = 1), that will be discarded by the isar 34. nom ? number of valid bytes in the mailbox indicates the number n of valid data bytes in the mailbox to be transmitted.
psb 7115 operational description semiconductor group 110 02.98 3.6 pump configuration 3.6.1 pump configuration setup (host ? isar 34) the pump is configured by the host. the host interrupt status register (his) indicates that a new pump configuration is available in the mailbox registers. important note: it is important to note that configuration of the pump will reset the whole data path except buffer configuration, i.e. any configuration of the sart and iom-2 is invalid, therefore the pump should be configured right after buffer configuration and precede sart and iom-2 configuration. the lsb of the control register holds the number of additional parameter words which are passed via the mailbox. the maximum number n of parameter words depends on the pump path mode. the message coding of configuration setup for some of the pump modes is similar in a few of the parameters, however the total message coding is described separately for each of the pump modes which are: table 10 pump modes mode pmod ? fax modulations ? datamodem modulations ? halfduplex modulations ? v.110 ?dtmf ?bypass 001 010 011 100 101 111
psb 7115 operational description semiconductor group 111 02.98 as the modulation based pump modes (pmod = 001, 010, 011) are not available in datapath 2, the second channel must not be configured to these pump modes. the table below shows to which of the pump modes datapath 2 can be configured. important note: it is important to note that datapath 2 must not be configured to v.110 if path 1 is configured to datamodem modulations at the same time. table 11 pump modes in path 1 and 2 datapath 1 (dps = 01) datapath 2 (dps = 10) fax modulations datamodem modulations halfduplex modulations v.110 v.110 (see note) dtmf bypass bypass
psb 7115 operational description semiconductor group 112 02.98 3.6.1.1 pump configuration setup - fax modulations (host ? isar 34) 76543210 dps msc mds his 01100110 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 76543210 ctrl lsb 4 76543210 1. parameter 0 0 0 0 0 atn 0 ctn 76543210 2. parameter 0 0 0 toa 76543210 3. parameter codd 76543210 4. parameter cldd oam ? originating/answering mode 00: reserved 01: pump is set to answering mode 10: pump is set to originating mode 11: reserved pmod ? pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass
psb 7115 operational description semiconductor group 113 02.98 atn ? answer tone enables or disables the generation of an answer tone when fax procedures are performed. 0: answer tone is disabled 1: answer tone is enabled ctn ? calling tone enables or disables the generation of a calling tone when fax procedures are performed. 0: calling tone is disabled 1: calling tone is enabled toa ? transmitter output attenuation 0: 0 db 1: 1 db : : 31: 31 db recommended value (if not otherwise specified): 6db. codd ... carrier on detect duration 0 - 253: this parameter specifies a time length in 100 ms units. carrier on (rlsd on) is signaled after a continuous carrier detection of the programmed time span. 254, 255: reserved recommended value (if not otherwise specified): 6 (600 ms) cldd ... carrier loss detect duration this parameter specifies a time length in 100 ms units. 0 - 253: carrier off (rlsd off) is signaled after a continuous carrier loss of the programmed time span. 254, 255: reserved recommended value (if not otherwise specified): 14 (1400 ms)
psb 7115 operational description semiconductor group 114 02.98 3.6.1.2 pump configuration setup - datamodem modulations (host ? isar 34) 76543210 dps msc mds his 01100110 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 76543210 ctrl lsb 11 7 6543210 1. parameter 0 0 v22b 0 v22 0 v21 bel 7 6543210 2. parameter amod v8 0 0 0 v34 v32 v23 7 6543210 3. parameter v32r (lsb) 15 14 13 12 11 10 9 8 4. parameter v32r (msb) 7 6543210 5. parameter v34r (lsb) 15 14 13 12 11 10 9 8 6. parameter v34r (msb) 7 6543210 7. parameter 0 0 0 0 gts atn ctn 7 6543210 8. parameter 0 0000000 7 6543210 9. parameter 0 0 0 toa
psb 7115 operational description semiconductor group 115 02.98 10 10. parameter codd 7 6543210 11. parameter cldd oam ? originating/answering mode 00: reserved 01: pump is set to answering mode 10: pump is set to originating mode 11: reserved pmod ? pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass v22b ? v.22bis, 2400 bit/s 0: is not permitted 1: is permitted v22 ? v.22/bell 212, 1200 bit/s 0: is not permitted 1: is permitted v21 ? v.21/bell 103, 300 bit/s 0: is not permitted 1: is permitted bel ? bell 103, 202 and 212 select bel selects whether in parameters v21, v22 and v23 the v.xx or the bell xxx modulation is selected. 0: bell modulation is not permitted 1: bell modulation is permitted amod ? automode operation according to eia/tia pn-2330 0: is disabled 1: is enabled 7 6543210
psb 7115 operational description semiconductor group 116 02.98 v8 ? v.8 negotiation 0: is disabled 1: is enabled v34 ? v.34 modulation 0: is not permitted 1: is permitted v32 ? v.32bis modulation 0: is not permitted 1: is permitted v23 ? v.23/bell 202, 1200 bit/s /75 bit/s 0: is not permitted 1: is permitted v32r ? v.32/v.32bis available rates v32r determines the rate signal (specified in itu v.32bis) that is used in the start-up, retrain and renegotiate procedures. the coding is the same as in the above mentioned recommendation, however some of the most commonly used codings are given below. 0000 0101 0001 0001: v.32, 4800 bit/s 0000 1101 0001 0001: v.32, up to 4800 bit/s 0000 0011 0001 0001: v.32, 9600 bit/s 0000 1111 0001 0001: v.32, up to 9600 bit/s 0000 1001 1101 0001: v.32bis, 7200 bit/s 0000 1101 1101 0001: v.32bis, up to 7200 bit/s 0000 1011 1001 0001: v.32bis, 9600 bit/s 0000 1111 1101 0001: v.32bis, up to 9600 bit/s 0000 1001 1011 0001: v.32bis, 12000 bit/s 0000 1111 1111 0001: v.32bis, up to 12000 bit/s 0000 1001 1001 1001: v.32bis, 14400 bit/s 0000 1111 1111 1001: v.32bis, up to 14400 bit/s v34r v.34 available rates v.34r determines the data rates which are permitted for both receive and transmit directions. a specific data rate is selected by a 1 in the corresponding bit position (unit is kbit/s). any combination of the data rates is allowed: 7 6 5 4 3 2 1 0 v.34r-lsb: 19.2 16.8 14.4 12.0 9.6 7.2 4.8 2.4 v.34r-msb: 0 0 33.6 31.2 28.8 26.4 24.0 21.6
psb 7115 operational description semiconductor group 117 02.98 the selection of the modulation scheme is contained from the 1st to the 6th parameter. if automode is selected, any modulation which is masked (set to 0) in one of the parameters, is not tested/used in automode operation. for non-automode the permitted modulation parameters are used to select the data modulation. if more than one modulation is permitted, the highest possible data rate is selected. the 8th parameter is reserved for further use and must be set to 0. gts ? guard tone select (for v.22/v.22bis) 00: guard tone disabled 01: 550 hz guard tone enabled 10, 11: reserved atn ? v.25 answer tone 0: disabled 1: enabled ctn ? ctn ? v.25 calling tone 0: disabled 1: enabled toa ? transmitter output attenuation 0: 0 db 1: 1 db : : 31: 31 db recommended value (if not otherwise specified): 6db codd ... carrier on detect duration 0 - 253: this parameter specifies a time length in 100 ms units. carrier on (rlsd on) is signaled after a continuous carrier detection of the programmed time span. 254, 255: reserved recommended value (if not otherwise specified): 6 (600 ms) cldd ... carrier loss detect duration this parameter specifies a time length in 100 ms units. 0 - 253: carrier off (rlsd off) is signaled after a continuous carrier loss of the programmed time span. 254, 255: reserved recommended value (if not otherwise specified): 14 (1400 ms)
psb 7115 operational description semiconductor group 118 02.98 3.6.1.3 pump configuration setup - halfduplex modulations (host ? isar 34) 76543210 dps msc mds his 01100110 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 76543210 ctrl lsb 5 76543210 1. parameter v17c v17d v29a v29b v29c v27a v27b v21 76543210 2. parameter 0 0 0 ept 0 0 v17a v17b 76543210 3. parameter 0 0 0 toa 76543210 4. parameter codd 76543210 5. parameter cldd oam ? originating/answering mode 00: reserved 01: pump is receiving only 10: pump is transmitting only 11: reserved pmod ? pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass
psb 7115 operational description semiconductor group 119 02.98 v17c ? v.17, 9600 bit/s 0: is disabled 1: is enabled v17d ? v.17, 7200 bit/s 0: is disabled 1: is enabled v29a ? v.29, 9600 bit/s 0: is disabled 1: is enabled v29b ? v.29, 7200 bit/s 0: is disabled 1: is enabled v29c ? v.29, 4800 bit/s 0: is disabled 1: is enabled v27a ? v.27ter, 4800 bit/s 0: is disabled 1: is enabled v27b ? v.27ter, 2400 bit/s 0: is disabled 1: is enabled v21 ? v.21 channel 2, 300 bit/s 0: is disabled 1: is enabled ept ? echo protector tone 0: is disabled 1: is enabled v17a ? v.17, 14400 bit/s 0: is disabled 1: is enabled v17b ? v.17, 12000 bit/s 0: is disabled 1: is enabled
psb 7115 operational description semiconductor group 120 02.98 the selection of the modulation scheme is contained in the 1st and 2nd parameter. if more than one modulation is enabled, the highest data rate is selected. toa ? transmitter output attenuation 0: 0 db 1: 1 db : : 31: 31 db recommended value (if not otherwise specified): 6 db. codd ... carrier on detect duration 0 - 253: this parameter specifies a time length in 100 ms units. carrier on (rlsd on) is signaled after a continuous carrier detection of the programmed time span. 254, 255: reserved recommended value (if not otherwise specified): 6 (600 ms) cldd ... carrier loss detect duration this parameter specifies a time length in 100 ms units. 0 - 253: carrier off (rlsd off) is signaled after a continuous carrier loss of the programmed time span. 254, 255: reserved recommended value (if not otherwise specified): 14 (1400 ms)
psb 7115 operational description semiconductor group 121 02.98 3.6.1.4 pump configuration setup - v.110 (host ? isar 34) 76543210 dps msc mds his 100110 15 14 13 12 11 10 9 8 ctrl msb 00000 pmod 76543210 ctrl lsb 2 76543210 1. parameter vdr 76543210 2. parameter 0000000fct dps ? datapath selection 01: path 1 10: path 2 pmod ? pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass
psb 7115 operational description semiconductor group 122 02.98 important note: in contrast to the recommended initialisation procedure described in chapter 3.1.4 , the sequence for configuration with pump mode v.110 is slightly different than for all other modes: if the pump should operate in v.110 mode, the iom-2 interface must be configured as the last functional block, i.e. the sequence for configuration setup should be 1. buffer configuration 2. pump configuration (v.110) 3. sart configuration 4. iom-2 configuration vdr ? v.110 data rate 3: 600 bit/s 4: 1200 bit/s 5: 2400 bit/s 6: 4800 bit/s 8: 9600 bit/s 12: 19200 bit/s 20: 38400 bit/s 21: 48000 bit/s 22: 56000 bit/s (default) 23: 56000 bit/s (alternative) 24: 64000 bit/s the default and alternative adaptation of 56 kbit/s to 64 kbit/s are specified in the itu-t v.110 recommendation. fct ? flow control (x-bits) 0: disabled 1: enabled if enabled, the received x-bits are evaluated by the pump control and data from the mailbox is not forwarded to the sart unit for transmission if indicated by the remote side. additionally, the x-bit change is indicated to the host by means of status events. flow control is only supported for sart mode v.14.
psb 7115 operational description semiconductor group 123 02.98 3.6.1.5 pump configuration setup - dtmf (host ? isar 34) 76543210 dps msc mds his 01100110 15 14 13 12 11 10 9 8 ctrl msb ddir 0 0 0 pmod 76543210 ctrl lsb 6 76543210 1. parameter rel 76543210 2. parameter tw_lsb 76543210 3. parameter tw_msb 76543210 4. parameter don 76543210 5. parameter doff 76543210 6. parameter 0 0 0 toa ddir ... dtmf direction control 00: reserved 01: dtmf transmitter active (no transfer of user data) 10: dtmf receiver active (during transfer of user data) 11: dtmf receiver and transmitter active (not supported in this version) transfer of user data is performed while a dtmf detector is active (ddir=10). in order to transmit dtmf tones the pump must temporarily be configured to "dtmf transmitter active" (ddir=01) and then reconfigured to "dtmf receiver active" (pmod=10) again.
psb 7115 operational description semiconductor group 124 02.98 pmod ? pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass rel ? rejection level (valid for dtmf receiver) a dtmf signal level which is below rel is not detected by the dtmf receiver. the table for all possible rel values is given below: 0: 0 dbm 1: C 1 dbm 2: C 2 dbm 3: C 3 dbm : : : : 93: C 93 dbm the unit dbm is given with respect to full scale. it is not recommended to use values above 93. recommended value (if not otherwise specified): 28 h = 40 d (C 40 dbm) tw twist (tw_msb, tw_lsb; valid for dtmf receiver) a dtmf tone consists of two tones with different frequency which have a signal level that can vary from another. the parameter twist defines the difference in level between both frequencies that is accepted by the isar 34. the isar 34 will not detect a dtmf tone if the corresponding level difference of the received frequencies is greater than twist. the parameter tw (= tw_msb, tw_lsb) is calculated according to the following equation, twist is the required level difference (to be inserted without its unit dbm): the unit dbm is given with respect to full scale. recommended value (if not otherwise specified): 1214 h = 4628 d (8 dbm) tw 2 15 10 twist 0 5 , + 10 ------------------------------ C =
psb 7115 operational description semiconductor group 125 02.98 in dtmf receive mode the octets received from the iom-2 timeslot are passed transparently through the pump without data formatting, similar to bypass mode. the dtmf receiver is active to detect dtmf tones in the received data stream and to indicate received dtmf digits to the host. the dtmf receiver interprets the octets received from the iom-2 timeslot as a-law or m -law pcm samples, depending on the iom-2 configuration. in transmit direction user data coming from the sart is forwarded similar as in bypass mode, i.e. without formatting in the pump. additionally dtmf tones can be generated by the pump which is transmitted to the iom-2. dtmf tone generation is performed by the host via dtmf specific pump control commands don ... dtmf on duration (valid for dtmf transmitter) defines the length of generated dtmf tones (coding see doff). doff ... dtmf off duration (valid for dtmf transmitter) a generated dtmf tone is subsequently followed by a signal pause. the length of this "no signal" phase is defined by doff. 0: (not to be used) 1: 1 ms 2: 2 ms : : 254: 254 ms 255: 255 ms the coding (given in decimal notation) is equal for don and doff. recommended value (if not otherwise specified): 80 ms (for both) toa ... transmitter output attenuation (valid for dtmf transmitter) 0: 0 db 1: 1 db : : 31: 31 db recommended value (if not otherwise specified): 6 db.
psb 7115 operational description semiconductor group 126 02.98 3.6.1.6 pump configuration setup - bypass mode (host ? isar 34) 76543210 dps msc mds his 100110 15 14 13 12 11 10 9 8 ctrl msb 0 0 0 dpw 0 pmod 76543210 ctrl lsb 0 dps ? datapath selection 01: path 1 10: path 2 dpw ? data path width 0: pump data path is 8 bit 1: pump data path is 16 bit pmod ? pump path mode select 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass
psb 7115 operational description semiconductor group 127 02.98 3.6.2 pump control command (host ? isar 34) control commands for the datapump are related to path 1 or path 2. for d-channel access via path 3 no pump is used, however commands to control the c/i-channel are coded with pump message codings.
psb 7115 operational description semiconductor group 128 02.98 3.6.2.1 pump control command - fax modulations (host ? isar 34) or 76543210 dps msc mds his 01101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb nom 76543210 1. parameter fcmdl 76543210 2. parameter fcmdh 76543210 3. parameter modc 76543210 3. parameter sld fcmd ? fax command (fcmdh, fcmdl) contains one of the following fax commands which are described in detail further down below. two (fcmdl and fcmdh) or three (fcmdl, fcmdh and modc or sld) additional parameter must be written to the mailbox. 00a7h: cmd_fth (nom = 3, 3rd parameter: modc) 00a5h: cmd_frh (nom = 3, 3rd parameter: modc) 00a8h: cmd_ftm (nom = 3, 3rd parameter: modc) 00a6h: cmd_frm (nom = 3, 3rd parameter: modc) 00ach: cmd_sil_det_on (nom = 3, 3rd parameter: sld) 00a2h: cmd_continue (nom = 2) 00a4h: cmd__escape (nom = 2) 00abh: cmd_sil_det_off (nom = 2) 00a9h: cmd_halt (nom = 2) nom ? number of additional parameters in the mailbox
psb 7115 operational description semiconductor group 129 02.98 the fax control commands of the isar 34 are focused on the fax class 1 standard, i.e. the commands have the same function as decribed therein. as for none of the other operation modes, the fax mode does not require a reprogramming of the complete data path when switching from hdlc formatted low speed data modulation (v.21ch2) to unformatted high speed data modulation (v.17, v.29, v.27ter) and vice versa. instead, by simply issuing a fax control command, both sart (binary or hdlc framing) and pump (v.21ch2, v.17, ...) are reprogrammed without affecting other configuration settings. modc ? modulation code this parameter indicates the particular facsimile modulation and speed selected for the next procedure. 3: 300 bit/s (v.21 ch2) 24: 2400 bit/s (v.27ter) 48: 4800 bit/s (v.27ter) 72: 7200 bit/s (v.29) 73: 7200 bit/s (v.17) 74: 7200 bit/s (v.17 with short train) 96: 9600 bit/s (v.29) 97: 9600 bit/s (v.17) 98: 9600 bit/s (v.17 with short train) 121: 12000 bit/s (v.17) 122: 12000 bit/s (v.17 with short train) 145: 14400 bit/s (v.17) 146: 14400 bit/s (v.17 with short train) sld ? silence duration this parameter determines the silence detect duration associated with the wait for silence procedure. 0: 0 1: 10 ms 2: 20 ms : : 255: 2550 ms
psb 7115 operational description semiconductor group 130 02.98 fax command description: : cmd_fth starts transmission of hdlc frames. the additional parameter modc (nom = 3) contains the modulation mode at which data is to be transmitted. cmd_frh starts reception of hdlc frames. the additional parameter modc (nom = 3) contains the modulation mode at which data is to be received. cmd_ftm starts transmission of binary data. the additional parameter modc (nom = 3) contains the modulation mode at which data is to be transmitted. cmd_frm starts reception of binary data. the additional parameter modc (nom = 3) contains the modulation mode at which data is to be received. cmd_sil_det_on starts to wait a determined length of time. the additional parameter sld (nom = 3) contains the silence duration which has to be waited. cmd_continue handshake message from the host to indicate that the host is ready to do the task (transmit/receive) which it selected before. cmd_escape this command is a regular escape in receive modes and a break in transmit modes. cmd_sil_det_off break of silence detection. cmd_halt shut down from fax pump idle state.
psb 7115 operational description semiconductor group 131 02.98 3.6.2.2 pump control command - datamodem modulations (host ? isar 34) command description: : 3.6.2.3 pump control command - halfduplex modulations (host ? isar 34) there are no control commands defined for this mode. 76543210 dps msc mds his 01101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 2 15 14 13 12 11 10 9 8 1. parameter dcmdl 15 14 13 12 11 10 9 8 2. parameter dcmdh dcmd ? datamodem command (dcmdh, dcmdl) contains one of the following datamodem commands, which are mainly used for debug purposes: 00ceh: local_renegotiate (only for v.34bis and v.32bis) 00cfh: local_retrain (only for v.34bis, v.32bis, v.32 and v.22bis) local_renegotiate initiates a v.34bis or v.32bis renegotiation, respectively. local_retrain initiates a v.34bis, v.32bis, v.32 or v.22bis retrain, respectively (depending on the selected modulation scheme).
psb 7115 operational description semiconductor group 132 02.98 3.6.2.4 pump control command - v.110 (host ? isar 34) or or or or or 76543210 dps msc mds his 101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 3 15 14 13 12 11 10 9 8 1. parameter vcmdl 76543210 2. parameter vcmdh 76543210 3. parameter (01f0h)000000 cct 76543210 3. parameter (01f1h)0000xsbsa1sa0 76543210 3. parameter (01f2h) 0 e1 e2 e3 e4 e5 e6 e7 76543210 3. parameter (01f3h) frc 76543210 3. parameter (01f4h) 1 76543210 3. parameter (01f5h) rof0 rof1 ron1 rofx ronx
psb 7115 operational description semiconductor group 133 02.98 dps ? datapath selection 01: path 1 10: path 2 vcmd ? v.110 command (vcmdh, vcmdl) contains one of the v.110 commands listed below. a third parameter must be written to the mailbox which is different for each of the commands. 01f0h: clamp control according to the parameter cct either user data (cct=00), 0-bits (cct=01) or 1-bits (cct=11) are transmitted. 01f1h: set s-,x-bits (for transmitter) the s- and x-bit setting is defined in the 3. parameter. 01f2h: set e-bits (for transmitter) the e-bit setting is defined in the 3. parameter. 01f3h: delay of synchronisation (for receiver) by default, frame synchronisation is achieved with the first v.110 frame that is received correctly. this command tells the pump control the number of v.110 frames which must be received correctly before synchronisation is achieved. the 3. parameter defines this number in the range 01h - ffh. 01f4h: enable mailbox buffer empty indication (for transmitter) if enabled, the isar 34 will release a status event to the host as soon as the last data in the mailbox buffer is transmitted and the host can set control bits after the last valid data has been transmitted. the status event will only be released once for a buffer empty condition, for a further state transition from not empty to empty, the indication has to be reenabled again. the 3. parameter must be set to 1. 01f5h: enable / disable dte control messages a status change of the remote dte is can be indicated to the host by status events (nom = 0). the host can select the type of status events to be received by enabling (1) or disabling the corresponding flag in the 3. parameter. for the v.110 commands set clamp to 0/1 (vcmd = 11h/13h) data must not be entered to the mailbox for transmission. if a clamp is set and continuous 0-bits or 1-bits are transmitted, mailbox data will be discarded by the isar 34.
psb 7115 operational description semiconductor group 134 02.98 the value 0 or 1 for each control bit below is directly written to the corresponding bit position within the v.110 frame: : nom ? number of additional parameters in the mailbox for some of the commands one additional parameter must be written to the mailbox. cct ? clamp control (required for command 01f0h) 00: clamp disabled (user data is transmitted) 01: clamp zero (0-bits are transmitted) 11: clamp one (1-bits are transmitted) x ? x-bit (required for command 01f1h) sb ? s4-, s9-bit (required for command 01f1h) sa1 ? s3-, s8-bit (required for command 01f1h) sa0 ? s1-, s6-bit (required for command 01f1h) e1-7 ? e1-, .. e7-bit (required for command 01f2h) for the 600 bit/s data rate bit e7 is don't care in the message coding, but is controlled by the pump for multiframe synchronisation. frc ? frame counter (required for command 01f3h) denotes the number of v.110 frames that must be received correctly in order to achieve synchronism, e.g. if frc = 3, three frames must be received correctly, before data is transferred to the receive buffer. rof0, rof1, ron1, rofx, ronx ... mask remote dte status indication (required for command 01f5h) indication of corresponding remote dte status is 0: disabled 1: enabled
psb 7115 operational description semiconductor group 135 02.98 3.6.2.5 pump control command - dtmf (host ? isar 34) 76543210 dps msc mds his 01101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb nom 76543210 1. parameter dcmdl 76543210 2. parameter dcmdh 76543210 3. parameter tdig dcmd dial command (dcmdh, dcmdl) 005ah: transmit dtmf digit (contained in 3. parameter, nom=3) all other codes not supported
psb 7115 operational description semiconductor group 136 02.98 it should be noted that the iom-2 interface must be configured with rate conversion enabled before any dtmf digits can be transmitted. 3.6.2.6 pump control command - bypass mode (host ? isar 34) there are no control commands defined for this mode. tdig ? transmit dtmf digit 10h: 0 11h: 1 12h: 2 13h: 3 14h: 4 15h: 5 16h: 6 17h: 7 18h: 8 19h: 9 1ah: a 1bh: b 1ch: c 1dh: d 1eh: * 1fh: #
psb 7115 operational description semiconductor group 137 02.98 3.6.2.7 pump control command - c/i-channel (host ? isar 34) 76543210 dps msc mds his 11101010 15 14 13 12 11 10 9 8 ctrl msb cic 76543210 ctrl lsb 0 cic c/i-channel command contains one of the following control commands for the c/i-channel. the function depends on whether d-channel access is configured with or without tic bus access (iom-2 configuration setup): ? tic bus disabled (iom-2 configuration setup: tic=0): 8mh: transmit c/i code m permanently this c/i code (coding is included in the low nibble m) is continuously transmitted on the c/i-channel without any mechanism for bus arbitration, i.e. bus access bit bac and tic bus address tad are not evaluated. ? tic bus enabled (iom-2 configuration setup: tic=1): 8mh: transmit c/i code m (no tic bus access) this c/i code (coding is included in the low nibble m) is continuously transmitted on the c/i-channel if no tic bus access is requested by the isar 34 and as long as bac=1 ("bus free") and tad=111 (tic bus address with lowest priority). once another device gains tic bus access, the c/i code m is no longer transmitted and the value 1111 b is transmitted on the c/i-channel by the isar 34. if the isar 34 gains tic bus access, the c/i code n (see below) is transmitted.
psb 7115 operational description semiconductor group 138 02.98 important note: before enabling the c/i-channel (iom-2 configuration setup with ced=1), both c/i codes (contained in cic=8mh and 9nh) must be programmed to ensure the right values are written to the c/i-channel from the beginning. 9nh: transmit c/i code n (tic bus access) this c/i code (coding is included in the low nibble n) is transmitted on the c/i-channel if the tic bus was accessed successfully (i.e. tic bus access mechanism is used by writing and reading back tad and evaluating bac). ? the command a0h is independent of tic bus configuration: a0h: request for current c/i code the host requests the isar 34 to read the current value on the c/i- channel. generally, subsequent c/i codes detected by the isar 34 are passed to the host in the sequence as they occured. the command a0h does not break this sequence. it forces the isar 34 to read the current value (even if theres no c/i code change) and forward it to the buffer. c/i codes are always read according to the "double last look" criterion, i.e. c/i codes are only accepted as valid if two consecutive values are identical.
psb 7115 operational description semiconductor group 139 02.98 3.7 pump status 3.7.1 pump status request (host ? isar 34) a status register which holds the current status of the data pump path is available on request. the pump status request is fully specified with the host interrupt status register (his). the mailbox control register is not used and must be written to 0. 76543210 dps msc mds his 001110 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 0 dps ? datapath selection 01: path 1 10: path 2
psb 7115 operational description semiconductor group 140 02.98 3.7.2 pump status response (isar 34 ? host) 3.7.2.1 pump status response - fax modulations (isar 34 ? host) 76543210 dps msc mds iis 01101110 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 76543210 ctrl lsb 2 76543210 1. parameter ril 76543210 2. parameter rim oam ? originating/answering mode 00: reserved 01: pump is in answering mode 10: pump is in originating mode 11: reserved pmod ? selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass
psb 7115 operational description semiconductor group 141 02.98 ril ? rate index - lsb ril contains the data rate at which the pump is currently operating. 0: no speed defined 2: 300 bit/s 5: 2400 bit/s 6: 4800 bit/s 7: 7200 bit/s 8: 9600 bit/s 9: 12000 bit/s 10: 14400 bit/s rim ? rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. if rim is 0, the preceding pump configuration setup was not successful. 0: no modulation scheme configured 21h: v.21 asynchronous (fsk v.14 mode) 27h: v.17 28h: v.29 2ch: v.27ter all other codes not supported.
psb 7115 operational description semiconductor group 142 02.98 3.7.2.2 pump status response - datamodem modulations (isar 34 ? host) 76543210 dps msc mds iis 01101110 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 76543210 ctrl lsb 5 76543210 1. parameter ril 76543210 2. parameter rim 76543210 3. parameter rit 76543210 4. parameter C C rrt lrt C rrp con neg 76543210 5. parameter C cld rty tmo C C rrn lrn oam ? originating/answering mode 00: reserved 01: pump is in answering mode 10: pump is in originating mode 11: reserved
psb 7115 operational description semiconductor group 143 02.98 pmod ? selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass ril ? rate index - lsb ril contains the data rate at which the pump is currently operating (same data rate in receive and transmit direction). for an asymmetrical data rate, ril indicates the receive data rate. 0: no speed defined 1: 75 bit/s 2: 300 bit/s 3: 600 bit/s 4: 1200 bit/s 5: 2400 bit/s 6: 4800 bit/s 7: 7200 bit/s 8: 9600 bit/s 9: 12000 bit/s 10: 14400 bit/s 11: 16800 bit/s 12: 19200 bit/s 13: 21600 bit/s 14: 24000 bit/s 15: 26400 bit/s 16: 28800 bit/s 17: 31200 bit/s 18: 33600 bit/s all other codes not supported.
psb 7115 operational description semiconductor group 144 02.98 rim ? rate index - msb rim contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. if rim is 0, the preceding pump configuration setup was not successful. 0: no modulation scheme configured 02h: v.22 09h: v.32 0ah: v.32bis 0bh: v.34 11h: v.21 asynchronous (fsk v.14 mode) 14h: v.23 27h: v.27ter 28h: v.29 2ch: v.17 51h: bell 103 54h: bell 202 all other codes not supported. rit ? rate index - transmit direction rit is only valid for v.34 modulation. it contains the data rate in transmit direction. 0: no speed defined 5: 2400 bit/s 6: 4800 bit/s 7: 7200 bit/s 8: 9600 bit/s 9: 12000 bit/s 10: 14400 bit/s 11: 16800 bit/s 12: 19200 bit/s 13: 21600 bit/s 14: 24000 bit/s 15: 26400 bit/s 16: 28800 bit/s 17: 31200 bit/s 18: 33600 bit/s all other codes not supported.
psb 7115 operational description semiconductor group 145 02.98 the status information is valid, if the corresponding bit is set: rrt ? remote retrain the pump is in a retrain phase that is initiated by the remote station. lrt ? local retrain the pump is in a retrain phase that is initiated by the local station. rrp ? retrain / renegotiate phase the pump is in a retrain or renegotiate phase. more details are contained in the status bits rrt, lrt, rrn and lrn. con ? connection the pump has established a logical connection to the remote subscriber, i.e. it has passed the training phase and will continue with data transmission/reception. neg ? negotiation the pump is in the first training phase to establish the modulation. cld ? cleardown this bit is set if there is a reason to terminate and restart the modulation. a reason could be a rate signal without any permitted data rate or a timeout condition for bulk delay (together with setting of tmo). rty ? retry during training phase the remote station has requested for a retrain (v.32bis only). tmo ? timeout during training phase the timing conditions for bulk delay were violated. rrn ? remote renegotiation the pump is in a renegotiate phase that is initiated by the remote station. lrn ? local renegotiation the pump is in a renegotiate phase that is initiated by the local station.
psb 7115 operational description semiconductor group 146 02.98 3.7.2.3 pump status response - halfduplex modulations (isar 34 ? host) 76543210 dps msc mds iis 01101110 15 14 13 12 11 10 9 8 ctrl msb oam 0 0 0 pmod 76543210 ctrl lsb 2 76543210 1. parameter ril 76543210 2. parameter rim oam ? originating/answering mode 00: not used 01: pump is receiving only 10: pump is transmitting only 11: not used pmod ? selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass
psb 7115 operational description semiconductor group 147 02.98 ril ? rate index - lsb ril contains the data rate at which the pump is currently operating. 0: no speed defined 2: 300 bit/s 5: 2400 bit/s 6: 4800 bit/s 7: 7200 bit/s 8: 9600 bit/s 9: 12000 bit/s 10: 14400 bit/s all other codes not supported. rim ? rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. if rim is 0, the preceding pump configuration setup was not successful. 0: no modulation scheme configured 21h: v.21 asynchronous (fsk v.14 mode) 27h: v.27ter 28h: v.29 2ch: v.17 all other codes not supported.
psb 7115 operational description semiconductor group 148 02.98 3.7.2.4 pump status response - v.110 (isar 34 ? host) 76543210 dps msc mds iis 101110 15 14 13 12 11 10 9 8 ctrl msb 00000 pmod 76543210 ctrl lsb 6 76543210 1. parameter ril 76543210 2. parameter rim 76543210 3. parameter C C C rof0 rof1 ron1 rofx ronx 76543210 4. parameter CCCCxsbsa1sa0 76543210 5. parameter C e1 e2 e3 e4 e5 e6 e7 76543210 6. parameter frc dps ? datapath selection 01: path 1 10: path 2
psb 7115 operational description semiconductor group 149 02.98 pmod ? selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass ril ? rate index - lsb ril contains the data rate at which the pump is currently operating. 0: no speed defined 3: 600 bit/s 4: 1200 bit/s 5: 2400 bit/s 6: 4800 bit/s 8: 9600 bit/s 12: 19200 bit/s 20: 38400 bit/s 21: 48000bit/s 22: 56000 bit/s (default) 23: 56000 bit/s (alternative) 24: 64000 bit/s all other codes not supported. ril = 0 is indicated in v.110 mode if not synchronised. rim ? rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. if rim is 0, the preceding pump configuration setup was not successful, e.g. a wrong data rate was selected for v.110. 0: no modulation scheme configured c0h: v.110 all other codes not supported.
psb 7115 operational description semiconductor group 150 02.98 note: x = dont care the following parameters contain the value for each x-, s- and e-bit, which is currently received: rof0, rof1, ron1, rofx, ronx ? remote dte status contains information about the status of the remote dte. the received d- and sa-bits are sampled and compared against different possibilities. a status change is detected by a match of the comparison and indicated by setting the bits as shown below. several bits in the parameter can be set simultaneously depending on the sampled data, e.g. if rof0 is set, rofx will be set, too. it should be noted, that the status response is not data related, i.e. it contains the remote status that is currently received. status status name sampled data rof0 remote (0, off) d sa 00000000 00000000 11111111 11111111 rof1 remote (1, off) d sa 11111111 11111111 11111111 11111111 ron1 remote (1, on) d sa 11111111 11111111 00000000 00000000 rofx remote (x, off) d sa xxxxxxxx xxxxxxxx 11111111 11111111 ronx remote (x, on) d sa xxxxxxxx xxxxxxxx 00000000 00000000 x ? x-bit sb ? s4-, s9-bit sa1 ? s3-, s8-bit sa0 ? s1-, s6-bit e1-e7 ? e1-bit - e7-bit for the 600 bit/s data rate bit e7 is always set to 1.
psb 7115 operational description semiconductor group 151 02.98 frc ? frame counter for delay of synchronisation denotes the actual number of frames that must be received correctly in order to achieve synchronism, e.g. if frc = 3, three frames have to be received correctly, before data is transferred to the receive buffer.
psb 7115 operational description semiconductor group 152 02.98 3.7.2.5 pump status response - dtmf (isar 34 ? host) 76543210 dps msc mds iis 01101110 15 14 13 12 11 10 9 8 ctrl msb ddir 0 0 0 pmod 76543210 ctrl lsb 2 76543210 1. parameter ril 76543210 2. parameter rim ddir ... dtmf direction control 00: reserved 01: dtmf transmitter active (no transfer of user data) 10: dtmf receiver active (during transfer of user data) 11: dtmf receiver and transmitter active (not supported in this version) pmod ? selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass ril ? rate index - lsb ril contains the data rate at which the pump is currently operating. 24: 64000 bit/s rim ? rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. c0h: digital transparent mode
psb 7115 operational description semiconductor group 153 02.98 3.7.2.6 pump status response - bypass mode (isar 34 ? host) 76543210 dps msc mds iis 101110 15 14 13 12 11 10 9 8 ctrl msb 00000 pmod 76543210 ctrl lsb 2 76543210 1. parameter ril 76543210 2. parameter rim dps ? datapath selection 01: path 1 10: path 2 pmod ? selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass ril ? rate index - lsb ril contains the data rate at which the pump is currently operating. 24: 64000 bit/s rim ? rate index - msb ril contains the modulation scheme at which the pump is currently operating, the specific data rate is given in ril. c0h: digital transparent mode
psb 7115 operational description semiconductor group 154 02.98 3.7.2.7 pump status response - pump disabled (isar 34 ? host) 76543210 dps msc mds iis 101110 15 14 13 12 11 10 9 8 ctrl msb 00000 pmod 76543210 ctrl lsb 0 dps ? datapath selection 01: path 1 10: path 2 pmod ? selected pump path mode 000: disable all (no mailbox entry) 001: fax modulations 010: datamodem modulations 011: halfduplex modulations 100: v.110 101: dtmf 111: bypass
psb 7115 operational description semiconductor group 155 02.98 3.7.3 pump status events (isar 34 ? host) status events are released to the host by the data pump during data transmission/ reception and contain dynamic information specific for the selected pump mode. 3.7.3.1 pump status events - fax modulations (isar 34 ? host) 76543210 dps msc mds iis 01101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 2 76543210 1. parameter fevtl 15 14 13 12 11 10 9 8 2. parameter CCCCC fevth fevt ? fax event (fevth, fevtl) contains the one of the following fax events: 002h: 10 ms timer interrupt (if enabled; see chapter 3.11.2 timer interrupt event) 0bch: rsp_ready 0b3h: line_tx_hdlc 0b2h: line_tx_binary 0b1h: line_rx_hdlc 0b0h: line_rx_binary 0b5h: rsp_connect 0b7h: rsp_disc 0b9h: rsp_fcerror 0beh: rsp_sil_det 0bah: flags_detect
psb 7115 operational description semiconductor group 156 02.98 fax event description : rsp_ready response to configuration fax mode originator or answerer. line_tx_hdlc response to cmd_fth in order to indicate that the modulation has been established. line_tx_binary response to cmd_ftm in order to indicate that the modulation has been established. line_rx_hdlc response to cmd_frh in order to indicate that the modulation has been established. line_rx_binary response to cmd_frm in order to indicate that the modulation has been established. rsp_connect indication that the fax pump is ready to receive or transmit data. rsp_disc indication that the fax pump has turned off modulation after transmitting all pending data / after the host issues the command cmd_escape. rsp_fcerror indication that the fax pump has detected a wrong modulation before it releases the event rsp_connect. rsp_sil_det indication that the prior selected duration of silence time has occured. flags_detect indication that the fax pump has detected flags.
psb 7115 operational description semiconductor group 157 02.98 3.7.3.2 pump status events - datamodem modulations (isar 34 ? host) 76543210 dps msc mds iis 01101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 2 76543210 1. parameter devtl 15 14 13 12 11 10 9 8 2. parameter CCCCC devth devt ? datamodem event (devth, devtl) contains the one of the following datamodem events: 002h: 10 ms timer interrupt (if enabled; see chapter 3.11.2 timer interrupt event) 018h: connection_on 019h: connection_off 020h: v24_off 021h: cts_on 022h: cts_off 023h: dcd_on 024h: dcd_off 025h: dsr_on 026h: dsr_off 0cch: remote_retrain 0cdh: remote_renegotiate 0d4h: gstn_cleardown
psb 7115 operational description semiconductor group 158 02.98 3.7.3.3 pump status events - halfduplex modulations (isar 34 ? host) 76543210 dps msc mds iis 01101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 2 76543210 1. parameter hevtl 15 14 13 12 11 10 9 8 2. parameter CCCCC hevth hevt ? halfduplex modulations event (hevth, hevtl) contains the one of the following datamodem events: 002h: 10 ms timer interrupt (if enabled; see chapter 3.11.2 timer interrupt event) 018h: connection_on 019h: connection_off 020h: v24_off 021h: cts_on 022h: cts_off 023h: dcd_on 024h: dcd_off 025h: dsr_on 026h: dsr_off 0d4h: gstn_cleardown
psb 7115 operational description semiconductor group 159 02.98 3.7.3.4 pump status events - v.110 (isar 34 ? host) or or 76543210 dps msc mds iis 101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb nom 76543210 1. parameter vevt_lsb 15 14 13 12 11 10 9 8 2. parameter C C C C C vevth 76543210 3. parameter C C C C x sb sa1 sa0 76543210 3. parameter C e1e2e3e4e5e6e7 76543210 3. parameter C C C rof0 rof1 ron1 rofx ronx dps ? datapath selection 01: path 1 10: path 2
psb 7115 operational description semiconductor group 160 02.98 vevt ? v.110 event (vevt_msb, vevt_lsb) contains one of the following v.110 events. for some of the events an additional parameter is provided via the mailbox. 002h: 10 ms timer interrupt (if enabled; see chapter 3.11.2 timer interrupt event) 1f1h: change in s-bits received (nom = 3). the s-bits are specified in the third parameter. 1f2h: change in e-bits received (nom = 3). the e-bits are specified in the third parameter. 1f8h: synchronisation lost (nom = 2). this event is released for a change from synchronised to not synchronised. 1f9h: synchronisation achieved (nom = 2). this event is released for a change from not synchronised to synchronised. 1f6h: change in x-bit from 1 ? 0 received (nom = 2). 1f7h: change in x-bit from 0 ? 1 received (nom = 2). 1f4h: mailbox buffer empty (nom = 2) this event indicates to the host, that the last data is transmitted and that the mailbox transmit buffer is empty. this event must be enabled by the host (see chapter 3.6.2.4 pump control command - v.110) and it is generated only once, i.e. for further state transitions from not empty to empty, the generation of the status event must be reenabled again. 1f5h: dte status (nom = 3) the third parameter contains information about the status of the remote dte. the received d- and sa-bits are sampled and compared against different possibilities. a status change is detected by a match of the comparison and indicated to the host. the generation of dte status events can be enabled/ disabled by control commands (see chapter 3.6.2.4 pump control command - v.110). nom ? number of valid bytes in the mailbox for certain status events one additional parameter is provided via the mailbox.
psb 7115 operational description semiconductor group 161 02.98 for the following parameters the received value 0 or 1 for each bit is indicated in the corresponding bit position. the control bits do not represent the real time value that is currently received, but they are data related, i.e. the s-, x- and e-bits are transferred to the host with the corresponding data that was received at the same time. information about control bits that are currently received can be requested by the host (see chapter 3.7.1 pump status request), additionally the real time value for x, which is needed for flow control, is indicated by two separate status events (vevt = 01f6h and 01f7h). x ? x-bit sb ? s4-, s9-bit sa1 ? s3-, s8-bit sa0 ? s1-, s6-bit e1-7 ? e1-, .. e7-bit for the 600 bit/s data rate bit e7 is always set to 1. rof0, rof1, ron1, rofx, ronx ? remote dte status contains information about the status of the remote dte. the received d- and sa-bits are sampled and compared against different possibilities. a status change is detected by a match of the comparison and indicated by setting the bits as shown below. several bits in the parameter can be set simultaneously depending on the sampled data, e.g. if rof0 is set, rofx will be set, too.
psb 7115 operational description semiconductor group 162 02.98 note: x = don't care it should be noted that the dte status information is data related and may not represent the value currently be received. comment: after reset the remote dte status logic is in no state and all status bits (rof0, rof1, ron1, rofx and ronx) are set to 0. the pump will start to search for frame synchronisation. when synchronisation is achieved, the host will receive the remote dte status and the s-, x- and e-bits from the pump by means of status events. this information is related to the last v.110 frame that was received for synchronisation, as this frame was received without any sync error. starting with the subsequent frame, the d-bits of the frame are transferred as valid user data to the sart. the same mechanism for resynchronisation is used if frame synchronisation is temporarily lost. table 12 v.110 remote dte status status status name sampled data rof0 remote (0, off) d sa 00000000 00000000 11111111 11111111 rof1 remote (1, off) d sa 11111111 11111111 11111111 11111111 ron1 remote (1, on) d sa 11111111 11111111 00000000 00000000 rofx remote (x, off) d sa xxxxxxxx xxxxxxxx 11111111 11111111 ronx remote (x, on) d sa xxxxxxxx xxxxxxxx 00000000 00000000
psb 7115 operational description semiconductor group 163 02.98 3.7.3.5 pump status events - dtmf (isar 34 ? host) 76543210 dps msc mds iis 01101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 3 76543210 1. parameter devtl 15 14 13 12 11 10 9 8 2. parameter CCCCC devth 76543210 3. parameter rdig devt ... dtmf event (devth, devtl) contains the one of the following dtmf events: 002h: 10 ms timer interrupt (if enabled; see chapter 3.11.2 timer interrupt event) 057h: dtmf tone detected (all other codes reserved)
psb 7115 operational description semiconductor group 164 02.98 3.7.3.6 pump status events - bypass mode (isar 34 ? host) no status events defined for this mode. rdig ? received dtmf digit one of the following dtmf digits was detected by dtmf receiver: 10h: 0 11h: 1 12h: 2 13h: 3 14h: 4 15h: 5 16h: 6 17h: 7 18h: 8 19h: 9 1ah: a 1bh: b 1ch: c 1dh: d 1eh: * 1fh: #
psb 7115 operational description semiconductor group 165 02.98 3.7.3.7 pump status events - d- and c/i-channel (isar 34 ? host) 76543210 dps msc mds iis 11101010 15 14 13 12 11 10 9 8 ctrl msb dcie 76543210 ctrl lsb 0 dcie ? d-channel and c/i-channel event contains one of the following events either from the d-channel or from the c/i-channel: 10h: message abort the isar 34 detects a s/g bit change to 1 (stop) and all d-channel data (i.e. current message and all subsequent messages) in the transmit buffer is cleared, the receive buffer is not affected. the host must write this data to the mailbox again, starting with the beginning of the aborted frame. however, the isar 34 has a short internal buffer for d-channel data to solve collisions on the s-bus, so not all collisions are indicated to the host, but handled automatically by the isar 34. therefore the "message abort" will only be released if the conflict could not be solved within the internal data storage of the isar 34. 20h: message complete a frame was successfully transmitted on the d-channel. this flag is used to control the transmission of subsequent d-channel hdlc frames. the host must not start writing data of a new hdlc frame to the isar 34 before this flag was set to confirm the successful transmission of the previous frame. 8mh: c/i code change m a new c/i code (coding is included in m) was received twice (double last look) on the c/i-channel (4th timeslot on iom-2 channel 0). when the c/i-channel is enabled by configuration setup, a first c/i code change message is indicated to the host with the current c/i information. the c/i information is not related to d-channel data.
psb 7115 operational description semiconductor group 166 02.98 3.8 iom a -2 configuration the following commands, requests and responses are used to setup/control the network access of the data paths. the message coding of both datapaths 1 and 2 (b-channel data) are similar. for datapath 3 (d-channel data) some codings are different and therefore described in separate chapters. 3.8.1 iom -2 configuration setup - path 1 and 2 (host ? isar 34) 76543210 dps msc mds his 100111 15 14 13 12 11 10 9 8 ctrl msb iom 0 0 0 cod rcv 76543210 ctrl lsb 5 76543210 1. parameter 0 0 0 txd rxd tsl 76543210 2. parameter 0 0 rtso 76543210 3. parameter 00000 rcs 76543210 4. parameter 0 0 ttso 76543210 5. parameter 00000 tcs dps ? datapath selection 01: path 1 10: path 2
psb 7115 operational description semiconductor group 167 02.98 iom ? iom-2 data access 0: disabled 1: enabled cod ? coding 000: no pcm coding (16-bit linear data) 001: a-law coding (8-bit data) 010: m -law coding (8-bit data) all other codes reserved for the pump modes v.110 and bypass no pcm coding must be selected. a-law and m -law coding is selected for all modulation related pump modes (fax, datamodem and halfduplex modulation, dtmf and dtmf transmission). if "no pcm coding" is selected in these modes, 16-bit linear values are output on the iom-2 interface. rcv ? rate conversion rcv refers to internal operation of the device and must be set depending on the pump mode. 0: disabled (for all other pump modes) 1: enabled (for pump modes 001, 010, 011, 110) txd ? transmit path switched to 0: dd-line 1: du-line (reset value) rxd ? receive path switched to 0: dd-line (reset value) 1: du-line tsl ? timeslot length for receive / transmit path 000: 8 bit wordlength (reset value) 010: 16 bit wordlength (used to operate with 16 linear codec, e.g. arcofi) all other codes currently not supported rtso ? receive time slot offset to fsc 0: 0 bit 1: 8 bit : : 63: 504 bit reset value: rtso = 0 for path 1 rtso = 1 for path 2
psb 7115 operational description semiconductor group 168 02.98 coding and timeslot length not all combinations of the cod and tsl parameters are supported. if the pump is configured to digital modes (v.110, pmod = 100) pcm coding has to be disabled (cod = 000). if the pump is configured to any of the other modes (fax, datamodem, halfduplex modulations, dtmf or dtmf transmission, pmod = 001, 010, 011, 101 or 110) either a-law (cod = 001) or m -law (pmod = 010) coding is selected to output an 8-bit pcm value to the iom-2 interface (tsl = 000). if 16-bit linear values should be provided for a codec, pcm coding is disabled (cod = 000) and timeslot length is 16 (tsl = 010). rcs ? receive clock shift 0: 0 bit 1: 1 bit : : 7: 7 bit reset value: rcs = 0 for path 1 and 2 ttso ? transmit time slot offset to fsc 0: 0 bit 1: 8 bit : : 63: 504 bit reset value: ttso = 0 for path 1 ttso = 1 for path 2 tcs ? transmit clock shift 0: 0 bit 1: 1 bit : : 7: 7 bit reset value: tcs = 0 for path 1 and 2
psb 7115 operational description semiconductor group 169 02.98 3.8.2 iom -2 configuration setup - path 3 (host ? isar 34) after an iom-2 configuration setup with d-channel enabled (ded=1), one data request message for buffer 3 will be released by the isar 34. every iom-2 configuration setup message will reset receive and transmit buffers for the d-channel (datapath 3) even if the specific configuration setting is not changed from a previous configuration (e.g. d- channel remains enabled ded=1). when the c/i-channel is enabled by configuration setup, a first c/i code change message is indicated to the host with the current c/i information. before enabling the c/ i-channel (configuration setup with ced=1), both c/i codes should be programmed (see chapter 3.6.2.7 ) to ensure the right values are written to the c/i-channel from the beginning. 76543210 dps msc mds his 1 1100111 15 14 13 12 11 10 9 8 ctrl msb ded tic ced 0 0 tad 76543210 ctrl lsb 0 ded ? d-channel enable/disable d-channel access is ... 0: disabled 1: enabled tic ? tic bus enable/disable access is performed ... 0: without tic bus 1: with tic bus ced ... c/i-channel enable/disable c/i-channel access is ... 0: disabled 1: enabled tad ... tic bus address the tic bus address is located in the fourth octet of the third subframe on the iom-2 du line. it is used for the tic-channel access procedure (if tic=1), enabling the connection of several layer-2 d-channel protocol controllers to the iom-2 interface.
psb 7115 operational description semiconductor group 170 02.98 3.8.3 iom -2 configuration request (host ? isar 34) the current configuration can be read on request by the host. the request is fully specified by the host interrupt status register (his), i.e. the control registers and the mailbox are not used for the request command and must be set to 0. two types of configuration request messages are defined depending on whether the messages is addressed to a specific datapath (path 1, 2 or 3) or general information on iom-2 configuration is requested: ? general configuration request: ? configuration request for specific channel: 76543210 dps msc mds his 00001000 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 0 76543210 dps msc mds his 000111 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 0 dps ? datapath selection 01: path 1 10: path 2 11: path 3
psb 7115 operational description semiconductor group 171 02.98 3.8.4 iom -2 configuration response - general code (isar 34 ? host) this is the repsonse to the general configuration request message specified in the previous chapter 3.8.3 . 76543210 dps msc mds iis 00101000 15 14 13 12 11 10 9 8 ctrl msb --dclamo---------- 76543210 ctrl lsb 0 dcl ? data clock 0: reserved for further use. 1: the bit clock on the iom-2 interface is twice the datarate. amo ? awake mode on if this bit is set to 1, the awake mode is active, i.e. the du line pulled to low by the isar 34. note: also see chapter chapter 3.8.7 for further information.
psb 7115 operational description semiconductor group 172 02.98 3.8.5 iom -2 configuration response - path 1 and 2 (isar 34 ? host) 76543210 dps msc mds iis 100111 15 14 13 12 11 10 9 8 ctrl msb iom 0 0 0 cod rcv 76543210 ctrl lsb 5 76543210 1. parameter 0 0 0 txd rxd tsl 76543210 2. parameter 0 0 rtso 76543210 3. parameter 00000 rcs 76543210 4. parameter 0 0 ttso 76543210 5. parameter 00000 tcs dps ? datapath selection 01: path 1 10: path 2 iom ? iom-2 data access 0: disabled 1: enabled
psb 7115 operational description semiconductor group 173 02.98 cod ? selected coding 000: no pcm coding (16-bit linear data) 001: a-law coding (8-bit data) 010: m -law coding (8-bit data) all other codes reserved a-law and m -law coding is selected for all modulation related pump modes (fax, datamodem and halfduplex modulation, dtmf and dtmf transmission). for all other modes (v.110 and bypass mode) no pcm coding must be selected. if "no pcm coding" is selected for modulation modes, 16-bit linear data is output on the iom-2 interface. rcv ? selected rate conversion rcv refers to internal operation of the device and is set depending on the pump mode. 0: disabled (for all other pump modes) 1: enabled (for fax modulations, datamodem modulations, halfduplex modulations and dtmf-transmission) txd ? transmit path switched to 0: dd-line 1: du-line (reset value) rxd ? receive path switched to 0: dd-line (reset value) 1: du-line tsl ? timeslot length for receive/transmit path 00x: 8 bit wordlength (reset value) 010: 16 bit wordlength all other codes currently not supported rtso ? receive time slot offset to fsc 0: 0 bit 1: 8 bit : : 63: 504 bit reset value: rtso = 0 for buffer 1 rtso = 1 for buffer 2
psb 7115 operational description semiconductor group 174 02.98 rcs ? receive clock shift 0: 0 bit 1: 1 bit : : 7: 7 bit reset value: rcs = 0 for buffer 1 and 2 ttso ? transmit time slot offset to fsc 0: 0 bit 1: 8 bit : : 63: 504 bit reset value: ttso = 0 for buffer 1 ttso = 1 for buffer 2 tcs ? transmit clock shift 0: 0 bit 1: 1 bit : : 7: 7 bit reset value: tcs = 0 for buffer 1 and 2
psb 7115 operational description semiconductor group 175 02.98 3.8.6 iom -2 configuration response - path 3 (isar 34 ? host) 76543210 dps msc mds iis 1 1100111 15 14 13 12 11 10 9 8 ctrl msb ded tic ced 0 0 tad 76543210 ctrl lsb 0 ded ? d-channel enable/disable 0: d-channel access is disabled 1: d-channel access is enabled tic ? tic bus enable/disable 0: access is performed without tic bus 1: access is performed with tic bus ced ... c/i-channel enable/disable 0: c/i-channel access is disabled 1: c/i-channel access is enabled tad ... tic bus address contains the programmed tic bus address.
psb 7115 operational description semiconductor group 176 02.98 3.8.7 iom -2 control commands - general code (host ? isar 34) the following control commands are not related to a specific datapath but to the iom-2 interface of the isar 34 in general. two types of command codings are differentiated regarding the interrupt status register coding (his) as shown below: in an isdn terminal for example the isar 34 can be connected to an s-transceiver (e.g. isac-s te psb 2186). for the transceiver the iom-2 interface can be switched off in the inactive state, reducing power consumption to a minimum. in this deactivated state the clock line is low and the data lines are high. for activation the transceiver enables the clock pulses again when the du line is pulled low by the isar 34, i.e. the c/i command tim = 0000 is received by the layer 1 device (= set awake mode on). 76543210 dps msc mds his 00101000 15 14 13 12 11 10 9 8 ctrl msb icmd 76543210 ctrl lsb 0 icmd ? iom-2 control command 20h: set awake mode on this command will pull the du line to low. 21h: set awake mode off this command will reset the du line to normal functionality.
psb 7115 operational description semiconductor group 177 02.98 76543210 dps msc mds his 00101001 15 14 13 12 11 10 9 8 ctrl msb icmd 76543210 ctrl lsb 0 icmd ? iom-2 control command 00h: restart isar 34 if the iom clocks are switched off (e.g. s-transceiver is in power down mode or missing clocks due to hardware malfunctions), the isar 34 enters a state where all datapaths are disabled. as soon as the clocks are available again, the isar 34 is made to leave the inactive state and to check for iom clocks. so this command is used to complete the power up procedure. after setting awake mode on and awake mode off (see command above) the host releases the restart isar 34 command and the isar 34 will enter the normal mode of operation.
psb 7115 operational description semiconductor group 178 02.98 3.8.8 iom -2 control commands - path 1 and 2 (host ? isar 34) 76543210 dps msc mds his 101011 15 14 13 12 11 10 9 8 ctrl msb icmd 76543210 ctrl lsb 0 dps ? datapath selection 01: path 1 10: path 2 icmd ? iom-2 control command 00h: stop iom-2 channel all activities on the iom-2 interface are frozen. in transmit direction all bits are written to 1 on the iom-2 timeslot and in receive direction all bits received from the iom-2 timeslot are 1. 01h: restart iom-2 channel after iom-2 activities were stopped (icmd = 00), data transfer from/to the iom-2 timeslots is restarted again with the current configuration settings. this command must not be used before the iom-2 interface is configured. 11h: loop on transmit data is looped back to the receiver input. in this case the configuration for the timeslot position of the receiver is without any effect. additionally, the transmit data itself is written to the programmed transmit timeslot if iom-2 data access is enabled (iom=1). if iom-2 data access is disabled (iom = 0), transmit data will not be written to the iom-2 timeslot but only looped back to the receiver input.
psb 7115 operational description semiconductor group 179 02.98 important note: the control commands stop / restart iom-2 channel have a different effect than iom- 2 data access enable / disable (iom-bit) in configuration setup. the current configuration setting is not affected by stop iom-2 channel, only transfer of user data between the pump and the iom-2 timeslots is stopped, which is resumed by the command restart iom-2 channel. 10h: loop off the loop of transmit data to the receiver input (activated by icmd = 11h) is switched off. regular read/write access to the iom-2 is performed according to the configuration setting.
psb 7115 operational description semiconductor group 180 02.98 3.8.9 iom -2 status events (isar 34 ? host) the following status event is not related to a specific datapath but to the iom-2 interface of the isar 34 in general. 76543210 dps msc mds iis 00101001 15 14 13 12 11 10 9 8 ctrl msb ievt 76543210 ctrl lsb 0 ievt ? iom-2 status event 00h: no iom-2 clocks the isar 34 indicates that no clocks are provided on the iom-2 interface. this may be due to the power down mode (e.g. s-transceiver switches off the clocks) or due to malfunctions of the system hardware. by releasing this message, the isar 34 enters an inactive state. it ceases to check for iom clocks and it disables all datapaths, i.e. sart, pump and iom-2 configuration are reset. however, all user data remains in the buffers and the contents of the receive buffers are sent to the host. this state can be left by the iom-2 control command restart isar 34.
psb 7115 operational description semiconductor group 181 02.98 3.9 monitor channel the functionality of the monitor channel handler is available within the datapath 0, so transfer of messages and data is performed via buffer 0. as the structure of these messages is quite different from the other datapaths, monitor channel messges are described separately in this chapter. only buffer related messages are identical for all datapaths and not described here. 3.9.1 buffer configuration and status the coding for buffer configuration and status messages is described in detail in chapters 3.1 and 3.3 . additionally the following information should be noted: ? transmit buffer the transmit buffer in datapath 0 is only used for monitor channel data. all other messages (host ? isar 34) which are related to datapath 0 are immediately executed and not transferred from the mailbox to the buffer. so a command to clear transmit buffer 0 will only affect monitor channel data. ? receive buffer the receive buffer in datapath 0 is not only used for monitor channel data. besides that also other messages (e.g. messages defined for datapath 0) are transferred via buffer 0.
psb 7115 operational description semiconductor group 182 02.98 3.9.2 monitor channel configuration 3.9.2.1 monitor channel configuration setup (host ? isar 34) a configuration setup for monitor channel will clear the transmit buffer of datapath 0 but not the receive buffer (see chapters 3.2 and 3.3 , buffer configuration and status). after configuration with monitor channel enable (mce=1) a data request for buffer 0 is released to the host to indicate that data can be written to the mailbox. 76543210 dps msc his 00110001 15 14 13 12 11 10 9 8 ctrl msb 0000000mce 76543210 ctrl lsb nom 76543210 1. parameter mam 76543210 2. parameter mra 76543210 3. parameter 0 0 0 slin csel mce ... monitor channel enable/disable monitor channel access is ... 0: disabled 1: enabled nom ... number of valid bytes in the mailbox if no parameters are written to the mailbox (nom=0), the previous settings are valid. not all parameters need to be written to the mailbox for configuration setup if the previous seetings of single parameters are valid, e.g. if slin and csel are still valid, only mam and mra with nom=2 need to be programmed.
psb 7115 operational description semiconductor group 183 02.98 mam ... monitor address mask every "1" in this byte marks the bit position where a check is done between the first byte of a received monitor data frame and the reference address (mra). the received monitor address will additionally be transferred to the host as the first data byte (see chapter 3.9.3.1 ). mra ... monitor reference address this is the reference address for the comparison with the first byte of a received monitor data frame. the bit positions which are not marked with a "1" in mam are dont care. slin ... serial line interface switching defines the switching of tx/rx data on du/dd lines. 0: transmit data on du, receive data from dd 1: transmit data on dd, receive data from du csel ... iom-2 channel select selects one of up to 16 channels on the iom-2 interface. the monitor channel is always the 3rd timeslot in an iom channel. 0000: channel 0 0001: channel 1 : : 1110: channel 14 1111: channel 15
psb 7115 operational description semiconductor group 184 02.98 3.9.2.2 monitor channel configuration request (host ? isar 34) the current configuration setting can be requested by the host. 3.9.2.3 monitor channel configuration response (isar 34 ? host) the current configuration setting is returned by the isar 34 on request. the coding is similar as for the configuration setup message ( chapter 3.9.2.1 ). 76543210 dps msc his 00010001 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 0 76543210 dps msc iis 00110001 15 14 13 12 11 10 9 8 ctrl msb 0000000mce 76543210 ctrl lsb 3 76543210 1. parameter mam 76543210 2. parameter mra 76543210 3. parameter 0 0 0 slin csel
psb 7115 operational description semiconductor group 185 02.98 3.9.3 monitor channel data 3.9.3.1 monitor channel receive data (isar 34 ? host) a status information is valid if the corresponding bit is set to "1": the end of a monitor message may be detected by the isar 34 some time after the last data byte was received and transferred to the host. therefore, it may occur that the end of a message is indicated in a message without valid data bytes (nom=0) and the last data byte of that monitor message was transferred to the host with the previous receive data message. 76543210 dps msc iis 00110000 15 14 13 12 11 10 9 8 ctrl msb -medmsd----- 76543210 ctrl lsb nom 76543210 1. parameter 1st databyte of the message 76543210 n. parameter n-th databyte of the message med ... message end detected the end of a monitor channel message is detected. msd ... message start detected the start of a monitor channel message is detected. the monitor address byte is provided as the first data byte in the mailbox. nom ... number of valid bytes in the mailbox indicates the number n of valid data bytes to be read from the mailbox.
psb 7115 operational description semiconductor group 186 02.98 3.9.3.2 monitor channel transmit data (host ? isar 34) a status information is valid if the corresponding bit is set to "1": 76543210 dps msc his 00110000 15 14 13 12 11 10 9 8 ctrl msb 0medmsd00000 76543210 ctrl lsb nom 76543210 1. parameter 1st databyte of the message 76543210 n. parameter n-th databyte of the message med ... message end the last byte written to the mailbox with this message is the last byte of the monitor message. msd ... message start the first byte written to the mailbox represents the beginning of the monitor message and is defined as the monitor address byte. nom ... number of valid bytes in the mailbox indicates the number n of valid data bytes written to the mailbox.
psb 7115 operational description semiconductor group 187 02.98 3.9.3.3 monitor channel status events (isar 34 ? host) the following status events are released by the isar 34 to indicate certain conditions related to the monitor channel. 76543210 dps msc iis 00110010 15 14 13 12 11 10 9 8 ctrl msb mevt 76543210 ctrl lsb 0 mevt ... monitor channel event contains one of the following events from the monitor channel: 10h: message abort the isar 34 has detected an abort from the receiver. all messages in the transmit buffer will be deleted. 20h: message complete the receiver has acknowledged the monitor message.
psb 7115 operational description semiconductor group 188 02.98 3.10 gpio (general purpose i/os) there are 9 general purpose i/os available in isar 34 that are free programmable by host messages. they can be configured as: ? input or output ? open drain or push pull ? continous or strobed sampling ? interrupt masked or unmasked
psb 7115 operational description semiconductor group 189 02.98 3.10.1 gpio configuration 3.10.1.1 gpio configuration - output register set/reset (host ? isar 34) the output register contains output values for all 9 gpio pins. if a gpio pin is configured as input (see below) the corresponding bit is ignored. for all gpios that are configured as output, the register reflects the value. after reset, all gpios are input. to achieve glitch-free output value after reset, you may write the output register first and then configure the corresponding pin(s) as output. the previously programmed value will then be output to the line. the gpios can be set or reset or left unaffected with the following command. 76543210 dps msc his 00101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 4 76543210 1. parameter r(7:0) 76543210 2. parameter 0000000r8 76543210 3. parameter s(7:0) 76543210 4. parameter 0000000s8 r(8:0) ... reset gpio 0: the corresponding gpio is unaffected 1: the corresponding gpio is reset to 0
psb 7115 operational description semiconductor group 190 02.98 setting and resetting a gpio in one command must be avoided. the reset value of the output register is 0. s(8:0) ... set gpio 0: the corresponding gpio is unaffected 1: the corresponding gpio is set to 1
psb 7115 operational description semiconductor group 191 02.98 3.10.1.2 gpio configuration - direction (host ? isar 34) the gpio direction can be set to input or output or left unaffected with the following command. setting a gpio to input and output in one command must be avoided. the reset value of the direction register is input. 76543210 dps msc his 00101010 15 14 13 12 11 10 9 8 ctrl msb 10h 76543210 ctrl lsb 4 76543210 1. parameter in(7:0) 76543210 2. parameter 0000000in8 76543210 3. parameter out(7:0) 76543210 4. parameter 0000000out8 in(8:0) ... set gpio to input 0: the corresponding gpio is unaffected 1: the corresponding gpio is set to input (reset) out(8:0) ... set gpio to output 0: the corresponding gpio is unaffected 1: the corresponding gpio is set to output
psb 7115 operational description semiconductor group 192 02.98 3.10.1.3 gpio configuration - open drain select (host ? isar 34) the gpio pins can be set to open drain or push/pull or left unaffected with the following command. setting a gpio to open drain and push/pull in one command must be avoided. the reset value of the gpios is open drain. when open drain is selected the internal pullup is enabled even if the gpio is configured as input. 76543210 dps msc his 00101010 15 14 13 12 11 10 9 8 ctrl msb 20h 76543210 ctrl lsb 4 76543210 1. parameter od(7:0) 76543210 2. parameter 0000000od8 76543210 3. parameter pp(7:0) 76543210 4. parameter 0000000pp8 od(8:0) ... set gpio to open drain 0: the corresponding gpio is unaffected 1: internal pullup enabled, gpio outputs are open drain (reset) pp(8:0) ... set gpio to output 0: the corresponding gpio is unaffected 1: internal pullup disabled, gpio outputs are push/pull
psb 7115 operational description semiconductor group 193 02.98 3.10.1.4 gpio configuration - strobed input (host ? isar 34) the read values of the gpio pins can be sampled continously (default) or in strobed mode. in the latter case pin 0 must be input and provides the strobe signal. for all other pins strobed mode can be individually enabled. if enabled, the pins are only sampled during pin 0 is low. state changes are ignored during pin 0 is high. the strobed input mode can be set or reset or left unaffected with the following command. 76543210 dps msc his 00101010 15 14 13 12 11 10 9 8 ctrl msb 30h 76543210 ctrl lsb 4 76543210 1. parameter c(7:0) 76543210 2. parameter 0000000c8 76543210 3. parameter s(7:0) 76543210 4. parameter 0000000s8 c(0) ... enable continous sampling 0: the corresponding gpio is unaffected 1: continous sampling is enabled (reset) c(8:1) ... set gpio to continous sampling 0: the corresponding gpio is unaffected 1: the corresponding gpio is continously sampled (reset)
psb 7115 operational description semiconductor group 194 02.98 setting a gpio to continous and strobed sampling in one command must be avoided. the reset value of the gpios is continous sampling. s(0) ... enable strobed mode sampling 0: the corresponding gpio is unaffected 1: strobed mode sampling is enabled s(8:1) ... set gpio to strobed mode sampling 0: the corresponding gpio is unaffected 1: the corresponding gpio is sampled in strobed mode if strobed mode is enabled (s(0)=1)
psb 7115 operational description semiconductor group 195 02.98 3.10.1.5 gpio configuration - interrupt mask (host ? isar 34) this command configures the general purpose pins which will send an event automatically when a state change is detected. when the interrupt mask is enabled for more than one pin, the host has to figure out which pin caused the event by comparing the new read status with the last one. the gpio interrupts can be masked or unmasked or left unaffected with the following command. setting and resetting a gpio interrupt mask in one command must be avoided. 76543210 dps msc his 00101010 15 14 13 12 11 10 9 8 ctrl msb 40h 76543210 ctrl lsb 4 76543210 1. parameter rm(7:0) 76543210 2. parameter 0000000rm8 76543210 3. parameter sm(7:0) 76543210 4. parameter 0000000sm8 rm(8:0) ... reset gpio interrupt mask 0: the corresponding gpio is unaffected 1: gpio interrupt mask is enabled, interrupt is disabled (reset) sm(8:0) ... set gpio interrupt mask 0: the corresponding gpio is unaffected 1: gpio interrupt mask is disabled, interrupt is enabled
psb 7115 operational description semiconductor group 196 02.98 the reset value of the gpio interrupts masks is 0 (interrupts disabled).
psb 7115 operational description semiconductor group 197 02.98 3.10.2 gpio status 3.10.2.1 gpio status request (host ? isar 34) the host requests the gpio status. the real status at the output pin is returned, independent of whether the pin is configured as input or output. when an output pin is configured as open drain, the status value may be different from the output value ("wired and"). 76543210 dps msc his 00001010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 0
psb 7115 operational description semiconductor group 198 02.98 3.10.2.2 gpio status event/response (isar 34 ? host) the gpio status may be an event or a response, depending on configuration. when the interrupt of a general purpose pin is enabled (imx=1) and the corresponding status changes, the new status of all 9 pins is reported to the host as a status event. independent of that the host may send a status request (see above). as a consequence the isar 34 will report the current status as a status response. note: gpio pins are sampled on a 10 msec basis. thus, the maximum switching frequency on a gpio should be less than 50 hz (maximum observable switching frequency). 76543210 dps msc iis 00101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 2 76543210 1. parameter st(7:0) 76543210 2. parameter xxxxxxxst8 st(8:0) ... reflects the current status of the general purpose pin. x ... dont care, maybe 1 or 0.
psb 7115 operational description semiconductor group 199 02.98 3.11 test/diagnostics path the test/diagnostics path is used for test and diagnostics, general configuration and control (not related to a specific data path) and as an answer channel for certain status/ configuration requests to the data channels. 3.11.1 timer interrupt on/off(host ? isar 34 ) 76543210 dps msc his 00100101 15 14 13 12 11 10 9 8 ctrl msb cmd 76543210 ctrl lsb 0 cmd ? command for general configuration 20h: timer interrupt off 21h: timer interrupt on if enabled, a 10 ms timer interrupt is generated to the host. this can be used for certain driver software implementations that require hardware interrupts. as this is normally used in applications with data modulations, the interrupt request message is coded as a message related to buffer 1 (see chapter 3.11.2 ), however, it can be used for purposes within other buffers, too. using the timer interrupt increases the message load between the isar 34 and the host significantly.
psb 7115 operational description semiconductor group 200 02.98 3.11.2 timer interrupt event (isar 34 ? host) the timer interrupt event message is generated once per 10 ms if enabled by the general configuration message in chapter 3.11.1 . 76543210 dps msc iis 01101010 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 2 76543210 1. parameter evtl 15 14 13 12 11 10 9 8 2. parameter CCCCC evth evt ... timer interrupt event (evth, evtl) 002h: 10 ms timer interrupt depending on the selected mode other pump mode specific events may be released to the host.
psb 7115 operational description semiconductor group 201 02.98 3.11.3 chip version request (host ? isar 34) the host can request the version number of the chip by the following request message. 3.11.4 chip version response (isar 34 ? host) the isar 34 returns the version number of the chip if requested by the host. important note: the chip version request and response messages are only valid after a hardware reset. these messages must not be used after the firmware download. 76543210 dps msc his 00100100 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 0 76543210 dps msc iis 00100101 15 14 13 12 11 10 9 8 ctrl msb 0 76543210 ctrl lsb 2 76543210 1. parameter cvnl 15 14 13 12 11 10 9 8 2. parameter cvnh cvn ? chip version number (cvnh, cvnl) 0101h: isar 34 version 2.1 all other codes currently not supported.
psb 7115 operational description semiconductor group 202 02.98 3.11.5 software version request (host ? isar 34) the host can request the version number of the dsp software by the following request message. 3.11.6 software version response (isar 34 ? host) the isar 34 returns the version number of the dsp software if requested by the host. 76543210 dps msc his 00000101 15 14 13 12 11 10 9 8 ctrl msb 10h 76543210 ctrl lsb 0 76543210 dps msc iis 00100101 15 14 13 12 11 10 9 8 ctrl msb 10h 76543210 ctrl lsb 2 76543210 1. parameter svnl 76543210 2. parameter svnh svn ? software version number (svnh, svnl) contains the version number of the dsp software on the device: 0101h: version 1.01 all other codes currently not supported.
psb 7115 operational description semiconductor group 203 02.98 3.11.7 request selftest result (isar 34 ? host) after download of the dsp program the isar 34 automatically performs a selftest, which will check for memory errors or missing iom-2 clocks. the result of the selftest can be requested by the host and possible error conditions are contained in the selftest response message (see chapter 3.11.8 ). 3.11.8 selftest response (isar 34 ? host) the selftest result requested by the host (see chapter 3.11.7 ) will result in a response message containing information about possible error conditions. 76543210 dps msc iis 00000100 15 14 13 12 11 10 9 8 ctrl msb 40h 76543210 ctrl lsb 0 76543210 dps msc iis 00100100 15 14 13 12 11 10 9 8 ctrl msb 40h 76543210 ctrl lsb 1 76543210 1. parameter 0 0 pro dro prr mb1 mb0 pll pro ... program rom error dro ... data rom error prr ? program ram error mb1 ? internal memory error (bank 1)
psb 7115 operational description semiconductor group 204 02.98 3.11.9 soft reset (host ? isar 34) the soft reset has a similar function as the hardware reset or power on reset. all configuration settings are reset and the buffers are cleared. mb0 ? internal memory error (bank 0) pll ? pll initialization error 76543210 dps msc his 00101000 15 14 13 12 11 10 9 8 ctrl msb rcmd 76543210 ctrl lsb 0 rcmd ? reset command 40h: soft reset, if dcl=0 (currently not supported) 41h: soft reset, if dcl=1 the command coding for the soft reset depends on the setting of the dcl parameter which can be read by a general iom-2 configuration request message (see chapter 3.8.3 ). the value of dcl is returned by the corresponding iom-2 configuration response message (see chapter 3.8.4 ). the isar 34 currently supports dcl=1 and rcmd=41h.
psb 7115 operational description semiconductor group 205 02.98 3.11.10 invalid message received (isar 34 ? host) if the host issues a message to the isar 34 with an his coding that is not specified, the isar 34 will respond with the following error message to indicate that an invalid message coding was detected. 76543210 dps msc iis 00111111 15 14 13 12 11 10 9 8 ctrl msb inv 76543210 ctrl lsb 0 inv ? invalid his coding contains the invalid his register coding of the message which was released by the host.
psb 7115 operational description semiconductor group 206 02.98 3.12 dsp program download in the isar 34 psb 7115 v2.1 the dsp program is downloaded through the host interface into the external memory. the binary file that includes the dsp program is provided together with the device. the data structure within the file is shown in figure 45 . figure 45 binary file structure the file is devided into a file header and a number of individual data blocks, each of which is preceeded by a block header. the file header contains general information such like file type identifier and version number. one data field contains the pointer block_ptr to the first block header ( figure 46 ). the block header defines the type of data contained in the subsequent data block, which implies the host to perform a certain action (e.g. read/write data from/to the isar 34, compare received message with given data, ... ). the data block contains the detailed information that is required by the host to perform that action. this includes complete message codings, data which transferred to the isar 34 and message codings for comparison of received messages. if the current data block is finished, a pointer (next_ptr) indicates to the start of the next block header. for certain types of data blocks a decision is made by the host so one of two pointers 7115_ 4 file - header block - header 1 data block 1 block - header 2 data block 2 block - header 3 data block 3
psb 7115 operational description semiconductor group 207 02.98 (true_ptr or false_ptr) is finally selected. if a timeout condition is specified for a data block the next valid block in case of a time out condition is indicated by timeout_ptr. all pointers are specified with respect to the beginning of the file. figure 46 pointer on data structures the following chapters show all details for the complete download mechanism. first the structure of the file header and the main routine for the program download is described. then follows the different types of block headers and how block headers must be be handled in general. the different block types are covered in separate chapters with flow charts that show how the host has to process the block data. file - header block - header 1 data block 1 block - header 2 data block 2 block - header 3 block_ptr next_ptr next_ptr 7115_46 file - header data block n block - header n+1 data block n+1 block - header n+3 true_ptr data block n+3 block - header x data block x false_ptr timeout_ptr
psb 7115 operational description semiconductor group 208 02.98 3.12.1 structure of file header the structure and contents of the file header are shown in table 14 . certain fields of data must be checked by the host. these are the file identification number (file_id), the product identification number (product_id) which must be within the given range and the block pointer (block_ptr) that indicates the beginning of the first block header. other data fields contain optional information that can be neglected such like the version number (version_no), the name of the device (product_name), the manufacturer identification (manufct_id), the header extension pointer (head_ext_ptr) and the timestamp of the file in pc format (timestamp). note: the offset of the individual data fields is indicated in bytes and decimal notation. the sequence of bytes for the field types "word" and "dword" within the binary file is least significant byte first. a blank space in the column "contents" is marked by an underscore " ". if the maximum length of the field is not used, the string is terminated by a zero byte (\00). as already mentioned in the previous chapter, the parameter block_ptr points to the beginning of the first block header with respect to the beginning of the file. table 13 structure of file header offset type field contents 0 byte [16] file_id "znelekre hcirlu\00" 16 byte [16] version_no "version 01.00 \00" 32 byte [16] product_name "isar 34, v2.1 \00" 48 byte [64] manufct_id "copyright 1997, siemens ag \00" 112 dword [1] product_id 00000010 h ... 00000015 h 116 dword [1] head_ext_ptr 00000000 h 120 dword [1] timestamp 124 dword [1] block_ptr
psb 7115 operational description semiconductor group 209 02.98 figure 47 download process 7115_62.a download start system board intialisation successful? abort open file and read file header yes no product_id correct ( = 10h ... 15h) ? abort no the parameter product_id must be a value in the given range. block header process yes download successful ? abort no download done yes file_id correct ? abort no yes
psb 7115 operational description semiconductor group 210 02.98 3.12.2 structure of block header the structure and contents of the block header are shown in table 14 . the block header is directly followed by the data block. the type of data contained in there is specified in the first data field block_type of the block header. all block_type codings for this version are listed in table 15 and described in detail in the following chapters. if the host reads a block_type parameter which is not described in this specification, the data block should be ignored and the next block header pointed to by unknown_ptr should be read. the following types of data blocks must be evaluated by the host. all other codings are reserved and should be ignored (see unknown_ptr). table 14 structure of block header offset type field contents 0 dword [1] block_type (see table 15 ) 4 dword [1] unknown_ptr table 15 types of data blocks block_type function 00000001 h jump to a specific block. 00000002 h write message to the isar 34. 00000003 h wait for next message from the isar 34. 00000004 h wait for a specific message from the isar 34. 00000005 h compare the last received message with given message coding. 00000006 h set coding information. 00000007 h set status information. 00000020 h write internal data memory. 00000021 h write internal program memory. 00000030 h write external data memory. 00000031 h write external program memory.
psb 7115 operational description semiconductor group 211 02.98 figure 48 block header process the pointer for the next block position (xxxx_ptr) is determined depending on the type of the current data block. the new pointer can be defined as next_ptr, true_ptr, false_ptr or timeout_ptr. block header process start read block header is block_type known ? execute data block process ignore this block pointer for next block position x_ptr = 0 ? set new pointer according x_ptr block header process done no yes yes no 7115_62.a set next block pointer x_ptr=unknown_ptr
psb 7115 operational description semiconductor group 212 02.98 3.12.3 structure of data blocks the data blocks directly follow the block header. the type of data block is indicated by the block_type parameter in the block header. the length of a data block can be fixed or variable, in the latter case a criteria is given in the specific data block for the block end. the structure and contents of the individual data blocks are described in the following chapters. a detailed description on how the host should treat each block is shown in a flow chart diagram. if the host is told to read or write a message from/to the isar 34 the general mechanisms for message transfer should be used as during normal operation mode (see chapter 3.1 ). 3.12.3.1 jump to block this data structure contains a single parameter. the host is told to jump to the next data block which is indicated by the pointer next_ptr. figure 49 data block process - jump to block table 16 block structure - block_type = 1 h offset type field 0 dword [1] next_ptr data block process (block_type= 1h) start set next block pointer = next_ptr data block process (block_type= 1h) done 7115_62.a read data block
psb 7115 operational description semiconductor group 213 02.98 3.12.3.2 write message this data block tells the host to write a message to the isar 34. the complete message coding is given in the data block. the coding for each of the message parameters is given in 16-bit words, however the msb is dont care and only the lsb is valid and written to the isar 34. the number of bytes (length of parameter mbox) which are written to the isar 34 mailbox are indicated by the parameter ctrl_lsb, so the length of the complete data block is not fixed but depends on the length of the mbox field. if the message is successfully written to the isar 34, the host jumps to the next block indicated by next_ptr. if the mailbox is not released by the isar 34 within a specified time (parameter timeout) the host proceeds with the next block indicated by timeout_ptr. both parameters are not given in this data block, but they are global variables (see chapter 3.12.3.6 ). note: for the data fields his, ctrl_msb, ctrl_lsb and mbox only the lsb values are evaluated. the msbs are dont care. the length of the mbox field n is determined by ctrl_lsb. table 17 block structure - block_type = 2 h offset type field 0 dword [1] next_ptr 4 word [1] his 6 word [1] ctrl_msb 8 word [1] ctrl_lsb 10 word [n] mbox
psb 7115 operational description semiconductor group 214 02.98 figure 50 data block process - write message data block process (block_type= 2h) start read data block isar 34 mailbox free (hia = 0) ? write message to the isar 34 set next block pointer = next_ptr set next block pointer = timeout_ptr timeout expired ? yes no no yes data block process (block_type= 2h) done 7115_62.a
psb 7115 operational description semiconductor group 215 02.98 3.12.3.3 wait for next message the next message that is received from the isar 34 is evaluated by the host. if this message is identical to the message coding given in the data block, then the host jumps to the block indicated by true_ptr. if the message coding is different, the next block to be processed by the host is indicated by fals_ptr. in case this message is not received within a specified time (parameter timeout) the host proceeds with the next block indicated by timeout_ptr. both parameters are not given in this data block, but they are global variables (see chapter 3.12.3.6 ). note: for the data fields iis, ctrl_msb, ctrl_lsb and mbox only the lsb values are evaluated. the msbs are dont care. the length of the mbox field n is determined by ctrl_lsb. received messages must always be stored by the host (see chapter 3.12.3.5 ). table 18 block structure - block_type = 3 h offset type field 0 dword [1] true_ptr 4 dword [1] false_ptr 8 word [1] iis 10 word [1] ctrl_msb 12 word [1] ctrl_lsb 14 word [n] mbox
psb 7115 operational description semiconductor group 216 02.98 figure 51 data block process - wait for next message data block process (block_type= 3h) start read data block new message received from isar 34 ? identical to reference message ? set next block pointer = true_ptr data block process (block_type= 3h) done set next block pointer = false_ptr set next block pointer = timeout_ptr timeout expired ? no no yes no yes yes the reference message is contained in the data block. 7115_62.a
psb 7115 operational description semiconductor group 217 02.98 3.12.3.4 wait for specific message the host compares all messages received from the isar 34 with the message coding given in the data block. if the required message is received, the host proceeds with the next block indicated by true_ptr. all other messages are discarded. if this message is not received within a specified time (parameter timeout) the host proceeds with the next block indicated by timeout_ptr. both parameters are not given in this data block, but they are global variables (see chapter 3.12.3.6 ). note: for the data fields iis, ctrl_msb, ctrl_lsb and mbox only the lsb values are evaluated. the msbs are dont care. the length of the mbox field n is determined by ctrl_lsb. received messages must always be stored by the host (see chapter 3.12.3.5 ). table 19 block structure - block_type = 4 h offset type field 0 dword [1] true_ptr 4 word [1] iis 6 word [1] ctrl_msb 8 word [1] ctrl_lsb 10 word [n] mbox
psb 7115 operational description semiconductor group 218 02.98 figure 52 data block process - wait for specific message data block process (block_type= 4h) start read data block new message received from isar 34 ? identical to reference message ? set next block pointer = true_ptr data block process (block_type= 4h) done set next block pointer = timeout_ptr timeout expired ? no no yes yes yes the reference message is contained in the data block. 7115_62.a no
psb 7115 operational description semiconductor group 219 02.98 3.12.3.5 compare last message generally, during the download procedure the host always has to store the last message received from the isar 34. a new message will always overwrite the previous one. in contrast to the last two chapters where the host waits for new messages, here the host compares the last message received from the isar 34 with the given message coding in the data block. if this message is identical to the given message coding the host jumps to the block indicated by true_ptr. if the message coding is different, the next block to be processed by the host is indicated by fals_ptr. note: for the data fields iis, ctrl_msb, ctrl_lsb and mbox only the lsb values are evaluated. the msbs are dont care. the length of the mbox field n is determined by ctrl_lsb. to store messages from the isar 34 the host should be prepared to store up to 256 byte of data from the mailbox (mbox). table 20 block structure - block_type = 5 h offset type field 0 dword [1] true_ptr 4 dword [1] false_ptr 8 word [1] iis 10 word [1] ctrl_msb 12 word [1] ctrl_lsb 14 word [n] mbox
psb 7115 operational description semiconductor group 220 02.98 figure 53 data block process - compare last message data block process (block_type= 5h) start read data block last message from isar 34 identical to reference message ? set next block pointer = true_ptr data block process (block_type= 5h) done set next block pointer = false_ptr no yes the last isar 34 message is stored in the host memory area, the reference message is contained in the data block. 7115_62.a
psb 7115 operational description semiconductor group 221 02.98 3.12.3.6 set coding information during the download procedures four global variables (timeout_ptr, timeout, his and ctrl_msb) are used for some of the data blocks. if a parameter (e.g. his or ctrl_msb) is not specified as a local variable in a specific data block, the parameter setting from the global variable is to be used. these global variables are initialized by the host when the procedures are started and they are modified when this data block occurs. the global variables are used by the data blocks block_type = 20 h , 21 h , 30 h and 31 h . some data blocks make use of a timer. the timeout value is specified in milliseconds [ms] by timeout. if a timeout condition occurs the host jumps to the next data block indicated by timeout_ptr. after the four variables are set the host jumps to the next block indicated by next_ptr. figure 54 data block process - set coding information table 21 block structure - block_type = 6 h offset type field initial value: 0 dword [1] next_ptr 4 dword [1] timeout_ptr 0 8 dword [1] timeout 0400 h (= 1024 ms) 12 word [1] his 0 14 word [1] ctrl_msb 0 data block process (block_type= 6h) start read data block store timeout_ptr timeout his ctrl_msb set next block pointer = next_ptr data block process (block_type= 6h) done 7115_62.a
psb 7115 operational description semiconductor group 222 02.98 3.12.3.7 set status information a status flag is used to indicate whether the complete download procedure succeeded or failed. this flag is not required for the download mechanism itself but it is used as an indication to the host. the host implements a variable status that is intialized with the value = ffff h and modified with every "set status information" block. when this block occurs the status flag must be set by the host according to the parameter status of the data block. after that the host jumps to the next block indicated by next_ptr. since the flag can be modified several times during the download the host must not evaluate it until the end of the download file is reached, i.e. the final information whether the download is successful or not is only valid after the download procedures are finished. the status flag indicates that the dsp program download was ... status = 0: ... successful status 1 0: ... not successful figure 55 data block process - set status information table 22 block structure - block_type = 7 h offset type field 0 dword [1] next_ptr 4 word [1] status data block process (block_type= 7h) start read data block store global variable status set next block pointer = next_ptr data block process (block_type= 7h) done 7115_62.a
psb 7115 operational description semiconductor group 223 02.98 3.12.3.8 write to memory the host writes data to the memory of the isar 34. four different block types are distinguished relating to the target memory to which data is downloaded, however the structure of the data blocks is identical and the download mechanism is rather similar. the host writes a message to the isar 34 that contains the code for program or data memory. the mechnism to write a message is shown in detail in the flow charts. the parameters like start_addr and length, as well as the code data (mbox) itself is contained in the data block. if the write message is acknowledged by the isar 34, the host jumps to the next data block indicated by true_ptr. if a different message than acknowledge is received, the next valid block is indicated by false_ptr. if a timeout condition occurs (parameter timeout) the host proceeds with the next block indicated by timeout_ptr. both parameters are not given in this data block, but they are global variables (see chapter 3.12.3.6 ). note: the length of the data field n is determined by length. table 23 types of memory write data blocks block_type function 00000020 h write internal data memory. 00000021 h write internal program memory. 00000030 h write external data memory. 00000031 h write external program memory. table 24 block structure - block_type = 20 h , 21 h , 30 h , 31 h offset type field 0 dword [1] true_ptr 4 dword [1] false_ptr 8 dword [1] start_addr 12 dword [1] length 16 word [n] data
psb 7115 operational description semiconductor group 224 02.98 figure 56 data block process - write to memory data block process (block_type= 20h, 21h, 30h or 31h) start read data block 7115_62.a initialize local variables len = length addr = start_addr numwords = 7ch the local variables len, addr and numwords are only valid and used during this block process. the parameters length and start_addr are contained in the data block. len = 0 ? set next block pointer = true_ptr data block process done isar 34 mailbox free (hia = 0) ? timeout expired ? set next block pointer = timeout_ptr data block process done yes no no no yes len < numwords ? block_type ? set numwords = len yes write message to isar 34: his (global variable) ctrl_msb (global variable) ctrl_lsb = 2 x numwords + 3 mbox[0] = b8-b15 of addr mbox[1] = b0-b7 of addr mbox[2] = numwords mbox[3] = msb of data 1 mbox[4] = lsb of data1 mbox[5] = msb of data 2 : : (note: b16-b31 of addr not used) write message to isar 34: his (global variable) ctrl_msb (global variable) ctrl_lsb = 2 x numwords + 4 mbox[0] = b0-b7 of addr mbox[1] = b8-b15 of addr mbox[2] = b16-b23 of addr mbox[3] = b24-b31 of addr mbox[4] = lsb of data1 mbox[5] = msb of data 1 mbox[6] = lsb of data 2 : : 0020h or 0021h 0030h or 0031h set len = len - numwords addr = addr + numwords timeout expired ? set next block pointer = timeout_ptr data block process done no yes new message received from isar 34 ? received message from isar 34 is acknowledge (iis = his + 1) ? set next block pointer = false_ptr data block process done no yes yes yes no no
psb 7115 operational description semiconductor group 225 02.98 3.13 fax class 1 implementation this chapter gives more details on the implementation of fax group 3 on the isar 34 psb 7115. it is expected that the controlling protocol residing on the host is either an implementation of the service class 1 command set (eia/tia-578) or itu-t t.30. it must be noted that for pump mode fax modulations, the sart unit is not to be configured as described in chapter 3.4 sart configuration. transmission and reception of hdlc framed and binary data is only controlled by pump control commands (see chapter 3.6.2.1 ) and pump status events (see chapter 3.7.3.1 ), i.e. the sart must not be reconfigured to hdlc or binary mode. however, data is transferred by use of sart data messages together with framing dependent control commands and status events (see chapters 3.5.1 and 3.5.2 sart data). fax pump control fax data transfer for configuration of the whole data path, first the buffer should be configured and then the pump and the iom-2 interface. configuration of sart and pump to the required framing and modulation scheme (e.g. hdlc framing and 300 bit/s /v.21ch2) is set by single pump control commands as mentioned above. further configuration data (modulation and silence duration) is passed by additional parameters to the pump control commands. ? pump control commands host ? isar 34 3.6.2.1 ? pump status events isar 34 ? host 3.7.3.1 ? sart control commands - along with transmit data host ? isar 34 3.5.2 ? sart status events - along with receive data isar 34 ? host 3.5.1
psb 7115 operational description semiconductor group 226 02.98 3.13.1 summary of isar 34 fax control commands cmd_fth starts transmission of hdlc frames. the sart is set to hdlc mode and the pump is set to modulation mode. the additional parameter contains the datarate of the pump modulation mode (v.21ch2) at which data is to be transmitted. cmd_frh starts reception of hdlc frames. the sart is set to hdlc mode and the pump is set to modulation mode. the additional parameter contains the datarate of the pump modulation mode (v.21ch2) at which data is to be received. cmd_ftm starts transmission of binary data. the sart is set to binary mode and the pump is set to modulation mode.the additional parameter contains the datarate of the pump modulation mode (v.17, v.29, v.27ter) at which data is to be transmitted. cmd_frm starts reception of binary data. the sart is set to binary mode and the pump is set to modulation mode.the additional parameter contains the datarate of the pump modulation mode (v.17, v.29, v.27ter) at which data is to be received. cmd_sil_det_on starts to wait a determined length of time. the additional parameter contains the silence duration which is to be waited. it is not mandatory and can be omitted , if the previous setting of this parameter is still valid. cmd_continue handshake message from the host to indicate that the host is ready to do the task (transmit/receive) which it selected before. cmd_escape this command is a regular escape in receive modes and a break in transmit modes. cmd_sil_det_off break of silence detection. cmd_halt shut down from fax pump idle state.
psb 7115 operational description semiconductor group 227 02.98 3.13.2 summary of isar 34 fax status events rsp_ready response to cmd_answer and cmd_originate line_tx_hdlc response to cmd_fth in order to indicate that the modulation has been established. line_tx_binary response to cmd_ftm in order to indicate that the modulation has been established. line_rx_hdlc response to cmd_frh in order to indicate that the modulation has been established. line_rx_binary response to cmd_frm in order to indicate that the modulation has been established. rsp_connect indication that the fax pump is ready to receive or transmit data. rsp_disc indication that the fax pump has turned off modulation after transmitting all pending data / after the host issues the command cmd_escape rsp_fcerror indication that the fax pump has detected a wrong modulation before it releases the event rsp_connect. rsp_sil_det indication that the prior selected duration of silence time has occured flags_detect indication that the fax pump has detected flags.
psb 7115 operational description semiconductor group 228 02.98 3.13.3 procedure termination in response to control commands generated by the host, the fax pump invokes various procedures. another procedure cannot be invoked until the previous procedure has been terminated. procedure termination may either be indicated by the fax pump or commanded by the host. the table below shows the termination indications and commands for each of the procedures. when no procedure is currently active, the fax pump is in an idle state. during the idle state, the command cmd_escape will be ignored by the fax pump, however, the host may issue the command cmd_halt to shut down the fax pump. this is normally done when a fax session has ended and the telephone connection is released. table 25 fax class 1 - procedure termination prodedure indication of procedure termination (isar 34 ? host) command for procedure termination (host ? isar 34) start as originator rsp_ready cmd_escape start as answerer rsp_ready cmd_escape hdlc transmit rsp_disc cmd_escape hdlc receive rsp_fcerror cmd_escape binary transmit rsp_disc cmd_escape binary receive rsp_fcerror cmd_escape wait for silence rsp_sil_det rsp_sil_det_off
psb 7115 operational description semiconductor group 229 02.98 3.13.4 fax pump startup procedure the host configures the fax pump either as originator or answerer when a physical connection has been established. after initialisation, the fax pump responds with rsp_ready, indicating, that it is ready for the next procedure. at this point the host must issue either a command cmd_frh or cmd_fth depending upon if the host is answering or originating a facsimile connection. the interaction of the host and the faxpump is as shown in the flow charts for transmission and reception of hdlc and binary data. figure 57 fax class 1 - startup procedure ata or atd establish physical connection, configure pump to fax originator/answerer event rsp_ready ? yes no abort character from dte ? no yes generate command cmd_halt teardown physical connection issue "ok" done proceed as with "at+fth=3" if answerer, or "at+frh=3" if originator 7115_51
psb 7115 operational description semiconductor group 230 02.98 3.13.5 hdlc transmission a host can control hdlc frame transmission during a fax group 3 session by issuing the command cmd_fth to the fax pump. hdlc transmission is specified by the t.30 procedure during the exchange of control information. some applications may alternatively implement hdlc framing directly, they would then use binary transmission for the transmission of their hdlc bit stream. , figure 58 fax class 1 - hdlc transmission at+fth= generate command cmd_fth (set parameter ) event line_tx_hdlc ? generate command cmd_continue event rsp_connect ? no yes no yes issue "connect" e seen ? 5 sec timeout expired ? b no yes no yes yes no data available from dte ? transfer data to fax pump mask frame_start onto 1st byte mask frame_end onto last byte last databyte sent ? b no yes no yes yes no seen ? final frame ? 7115_52 e
psb 7115 operational description semiconductor group 231 02.98 3.13.6 binary transmission a host can control binary transmission during a fax group 3 session by issuing the command cmd_ftm to the fax pump. binary transmission is specified by the t.30 procedure during the exchange of image. figure 59 fax class 1 - binary transmission at+ftm= generate command cmd_continue generate command cmd_ftm (set parameter ) event line_tx_bin ? event rsp_connect ? issue "connect" data from dte ? 5 sec timeout expired? transfer dte data to fax pump buffer empty ? last dataword nul ? seen ? buffer empty ? 5 sec timeout expired? seen ? e b b e b no yes no yes yes no yes yes yes no no yes no no yes no no yes yes no 7115_53
psb 7115 operational description semiconductor group 232 02.98 3.13.7 hdlc reception a host can control hdlc frame reception during a fax group 3 session by issuing the command cmd_frh to the fax pump. hdlc reception is specified by the t.30 procedure during the exchange of control information. some applications may alternatively implement hdlc framing directly, they would then use binary reception for the reception of their hdlc bit stream. figure 60 fax class 1 - hdlc reception at+frh= generate command cmd_frh (set parameter ) event rsp_connect ? yes no event rsp_fcerror ? yes no no yes a generate continue event line_rx_hdlc ? yes no event rsp_fcerror ? abort character from dte ? yes no no yes a c issue "connect" transfer data from fax pump to dte no no no yes abort character from dte ? du_frame_end seen ? no_more_data flag seen ? send to dte a d b done yes no frame received correctly ? issue "ok" generate command cmd_escape no yes same frh command ? different command ? c abort character from dte ? send to dte send to dte no yes yes 7115_54 yes
psb 7115 operational description semiconductor group 233 02.98 3.13.8 binary reception a host can control binary reception during a fax group 3 session by issuing the command cmd_frm to the fax pump. binary reception is specified by the t.30 procedure during the exchange of image. figure 61 fax class 1 - binary reception at+frm= generate command cmd_frm (set parameter ) no yes no yes no yes event line_rx_binary ? event rsp_fcerror ? abort character from dte ? a c generate command cmd_continue no yes no yes no y event rsp_connect ? event rsp_fcerror ? abort character from dte ? a c issue "connect" transfer data from fax pump to dte no yes no yes no_more_data flag seen ? abort character from dte ? send to dte a d send to dte 7115_55
psb 7115 operational description semiconductor group 234 02.98 3.13.9 call termination figure 62 fax class 1 - call termination 3.13.10 procedure terminations figure 63 fax class 1 - procedure terminations ath generate command cmd_halt teardown physical connection issue "ok" done 7115_56 generate cmd_escape issue "ok" done d c b a generate cmd_escape generate cmd_escape generate cmd_escape issue "error" issue "fcerror" issue "no carrier" done done done issue dummy data byte with no_more_data flag set issue "ok" done e 7115_56
psb 7115 operational description semiconductor group 235 02.98 3.14 startup procedures after a physical connection between two modems has been established, certain procedures can be started before signals are exchanged which are specific to a particular modem standard (v.34bis, v.32bis, ... ). these procedures are used to determine the type of modulation at which data is transferred right after completion of the startup procedure. the isar 34 is able to make use of the negotiation standard itu-t v.8 and the automode operation according to eia/tia pn-2330, which are described in the following chapters. after the host configures the datapump to data modem modulations with startup procedures (v.8, automode) enabled, it can request the selected modulation scheme from the isar 34 as soon as the modulation has been established between both modems. 3.14.1 v.8 negotiation in v.8 mode the answerer starts with transmitting the answer tone ansam and monitors the reception of the call tone. if the originator does not indicate v.8 capability or the v.8 procedures fail, the isar 34 will proceed with automode answerer operation. figure 64 v.8 answering mode connect to line answering mode send ansam, monitor signals call tone (ci) signal detected ? done yes proceed with automode (answerer) operation no 7115_61.a v.8 signalling successful ? no yes
psb 7115 operational description semiconductor group 236 02.98 the v.8 originator starts with transmission of the call tone while monitoring for the answering tone. if the answerer does not indicate v.8 capability or the v.8 procedures fail, the isar 34 will proceed with automode originator operation. figure 65 v.8 originating mode v.34bis modulation can only be achieved by using the v.8 negotiation mechansim as the automode operation does not provide for the upgrade from v.32bis to v.34bis. in other words, if v.8 is not used or v.8 fails, v.34bis modulation can not be selected. 3.14.2 automode operation automode selection is available based on eia/tia pn-2330. when enabled, the datapump will determine the communication standard supported by the remote modem and configure itself according. that means the modulation scheme and the data rate is automatically set without any host control. the following figures show the flowcharts corresponding to the dsp algorithm used in supporting automode originating and answering mode. the signals indicated in both figures relate to the itu-t v.32bis specification. connect to line originating mode send call tone, monitor signals answer tone ansam signal detected ? yes proceed with automode (originator) operation no 7115_61.a done v.8 signalling successful ? no yes
psb 7115 operational description semiconductor group 237 02.98 figure 66 automode answerer automode answering mode send answer tone (2100 hz), monitor signals aa detected or ans timeout (3.6 s)? v.32bis aa send usb1, monitor signals start timer (1000 ms) timeout 1270 hz, 980 hz, s1, sb1 detected or timeout? bell 103 v.21 v.22 v.22bis 1270 hz 980 hz sb1 s1 timeout stop usb1, send ac, start timer (800 ms) aa detected or timeout ? v.32bis aa timeout stop ac, transmit 1650 hz, start timer (2000 ms) 1270 hz, 980 hz detected or timeout ? v.21 980 hz bell 103 1270 hz timeout stop 1650 hz, transmit 1300 hz, start timer (2000 ms) 390 hz detected or timeout ? v.32bis v.23 390 hz timeout s1, sb1 detected or timeout? v.22 v.22bis sb1 s1 send usb1, monitor signals start timer (2000 ms) timeout 7115_61.a
psb 7115 operational description semiconductor group 238 02.98 figure 67 automode originator automode originating mode monitor signals 1650 hz, 1300 hz, 2225 hz, ac, usb1 or ans ? v.23 ac v.32bis v.21 1650 hz 1300 hz monitor signals, start timer (3100 ms) usb1, 2225 hz ac detected or timeout ? v.32bis ac send s1 / sb1, start timer (2140 ms) timeout s1/sb1 detected or timeout ? v.22 / v.22bis s1 or sb1 bell 103 timeout 1 second delay send aa, start timer wait for end of ans -> stop timer 1650 hz, 1300 hz, 2225 hz, ac or usb1 ? v.23 ac v.32bis v.21 1650 hz 1300 hz usb1, 2225 hz timer < 800 ms ? ans no yes 7115_61.a
psb 7115 summary of messages semiconductor group 239 02.98 4 summary of messages dps buffer configuration setup functional bl ock mode message type read/ wr i t e his / iis ctrl msb ctrl lsb 1. parameter 2. parameter 3. parameter 4. parameter 5. parameter ... parameters wr rd 0 0 0 0 0 0 0 0 1 0 0 1 0 1 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 1 1 0 pump 0 0 0 0 0 bbp 1 mml buffer configuration request wr 00 buffer configuration response - - - - - bbp 2 mml mpl buffer control command wr 0 0 0 0 0 0 crb 0 buffer buffer status request wr 0 0 0 0 0 0 0 sts 0 status response rd - - - - rdm3 -2 -1 -0 6 nbrl nbrm nmr nbtl nbtm nmt buffer status event - specific rd stev 0 buffer status event - general rd 0 sart configuration setup hdlc wr hdmc 0 0 smode 1 0 0 0 hio iff flen edf duo sart configuration setup async wr sart configuration setup bi nary wr hdmc 0 0 smode hdmc 0 0 smode 2 0 ovsp snp psl edp nsb chs bft 0 0 0 0 0 0 duo bsw dufw 2 1 0 0 1 0 1 1 0 0 1 0 1 sart hdlc sart async sart binary status event with receive data status event wi th recei ve data status event wi th recei ve data rd rd rd 1 0 0 0 0 0 1 0 0 0 0 0 - fed fsd fad rer cer- nmd nom 1st data byte 2nd data byte .... data bytes - - bre brs dsd per - - nom 1st data byte 2nd data byte .... data bytes - - - - - - - nmd nom 1st data byte 2nd data byte .... data bytes sart hdlc sart async sart bi nary control command wit h transmi t data control command wit h transmi t data control command wit h transmi t data wr wr wr 1 0 0 0 0 0 1 0 0 0 0 0 0 fed fst gfa 0 0 0 nmd 0 0 0 0 0 0 0 nmd nom 1st data byte 2nd data byte .... data bytes nom 1st data byte 2nd data byte .... data bytes nom 1st data byte 2nd data byte .... data bytes 0 0 sob sab dsb v42 0 0 pump fax modulati ons configuration setup wr wr configuration setup dat amodem modul at i ons 0 1 1 0 0 1 1 0 oam 0 0 0 pmod oam 0 0 0 pmod 0 0 0 0 0 atn 0 ctn 0 0 0 toa 0 0 0 toa 0 0 v22b 0 v22 0 v21 bel amod v8 0 0 0 v34 v32 v23 v32r (lsb) v32r (msb) 0 0 0 0 gts atn ctn 0 1 dps dps dps dps dps dps msc 0 0 msc 0 0 msc 0 0 msc mds msc mds msc mds msc mds dps dps dps dps dps dps dps dps dps sart disabled configuration setup wr 0 0 0 0 smode 1 0 0 1 0 1 dps 2 0 - - - - rdm3 -2 -1 -0 4 11 codd cldd v34r (lsb) v34r (msb) codd cldd 7115_70 0 0 0 0 0 0 0 0
psb 7115 summary of messages semiconductor group 240 02.98 functional block mode message type read/ wr i t e his / iis ctrl msb ctrl lsb 1. parameter 2. parameter 3. parameter 4. parameter 5. parameter ... parameters 1 0 1 0 1 0 0 0 1 1 1 0 pump wr configuration setup halfduplex modulations 1 0 0 1 1 0 oam 0 0 0 pmod 0 0 0 toa v17c v17d v29a v29b v29c v27a v27b v21 0 0 0 ept 0 0 v17a v17b pump wr configuration setup v. 110 dps 0 0 0 0 0 pmod pump pump pump configuration setup configuration setup wr wr wr 2 vdr 0 0 0 0 0 0 0 fct bypass dtmf ddir 0 0 0 pmod 0 0 0 0 0 pmod 6rel 0 0 0 toa 0 pump pump pump pump fax modulati ons datamodem modul ati ons halfduplex modulations v. 110 bypass control command control command control command control command control command control command pump wr wr wr wr wr 0 nom modc or sld 2 03 0 0 0 0 x sb sa1 sa0 not defined dcmdl not defined pump pump pump pump pump fax modulati ons halfduplex modulations v. 110 bypass dtmf pump wr rd status request datamodem modul ati ons 1 0 1 1 1 0 00 pump (all modes) status response rd status response status response rd status response rd status response rd status response 1 0 1 1 1 0 1 0 1 1 1 0 1 0 1 1 1 0 oam 0 0 0 pmod oam 0 0 0 pmod oam 0 0 0 pmod 2rilrim 2rilrim - cld rty tmo - - rrn lrn rd rd 6rilrim - - - rof0 rof1 ron1 rofx ron x - - - - x sb sa1 sa0 - e1 e2 e3 e4 e5 e6 e7 frc 2rilrim 2rilrim 1 0 1 1 1 0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 ril rim - - rrt lrt - rrp con neg dps dps dps dps dps 0 0 0 0 0 pmod codd cldd 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 fcmdl fcmdh dcmdl dcmdh 0 e1 e2 e3 e4 e5 e6 e7 frc or: or: 03 tdig dcmdh pump c/i-channel control command wr 1 1 1 0 1 0 1 0 cic 0 rit 7115_71 0 tw_lsb tw_msb don doff dtmf vcmdl vcmdh 0 0 0 0 0 0 0 cct or: or: 1 0 0 0 rof0 rof1 ron1 rofx ronx or: 5 pump disabled status response rd dps 1 0 1 1 1 0 0 0 0 0 0 pmod 0 0 0 0 0 pmod 1 0 1 1 1 0 0 5 ddir 0 0 0 pmod
psb 7115 summary of messages semiconductor group 241 02.98 0 1 1 0 1 0 1 0 functional block mode message type read/ wr i t e his / iis ctrl msb ctrl lsb 1. parameter 2. parameter 3. parameter 4. parameter 5. parameter ... parameters dps 1 0 1 0 1 0 1 0 1 0 0 0 pump pump pump pump fax modulations hal fduplex modulations v. 110 bypass dtmf pump rd datamodem modulations pump rd rd rd rd status events 0 1 1 0 1 0 1 0 0 1 1 0 1 0 1 0 status events status events status events status events - - - - - devth 2 devtl hevtl nom - - - - x sb sa1 sa0 rdig 3 status events rd not defined iom-2 configuration setup - path 1 and 2 wr 1 0 0 1 1 1 i om 0 0 0 cod rcv 5 0 0 0 txd rxd tsl 0 0 rtso 0 0 0 0 0 rcs 0 0 ttso 0 0 0 0 0 tcs iom-2 configuration request - specific wr 0 0 0 1 1 1 0 0 iom-2 configuration response - path 1 and 2 rd 1 0 0 1 1 1 i om 0 0 0 cod rcv 5 0 0 0 txd rxd tsl 0 0 rtso 0 0 0 0 0 rcs 0 0 ttso 0 0 0 0 0 tcs iom-2 control command - general wr icmd 0 dps dps dps 0 0 0 2 2 - - - - - fevth - - - - - hevth fevtl - e1 e2 e3 e4 e5 e6 e7 - - - rof0 rof1 ron1 rofx ronx or: or: pump d- and c/i- channel rd rd 1 1 1 0 1 0 1 0 status events dci e 0 iom-2 configuration setup - path 3 wr 1 0 0 1 1 1 ded tic ced 0 0 tad 0 1 1 iom-2 configuration request - general wr 0 0 1 0 0 0 0 0 0 0 iom-2 configuration response - general rd 1 0 1 0 0 0 - dcl amo - - - - - 0 0 0 iom-2 configuration response - path 3 rd 1 0 0 1 1 1 0 ded ti c ced 0 0 tad 1 1 1 0 1 0 0 1 icmd 0 1 0 1 0 1 1 iom-2 control command - path 1 and 2 wr icmd 0 dps 0 0 0 0 1 0 1 0 0 1 iom-2 status events rd ievt 0 0 0 7115_72 0 1 1 0 1 0 1 0 devtl 0 0 - - - - - vevth - - - - - devth vevtl
psb 7115 summary of messages semiconductor group 242 02.98 functional block mode message type read/ write his / iis ctrl msb ctrl lsb 1. parameter 2. parameter 3. parameter 4. parameter 5. parameter ... parameters 0 0 1 0 0 1 0 1 0 0 0 0 0 1 0 1 0 0 1 0 0 1 0 1 test/diag. test/diag. test/diag. timer interrupt on / off wr svnl 0 software version request wr 10h 0 software version response rd 10h 2 test/diag. timer interrupt event rd 0 1 1 0 1 0 1 0 cmd test/diag. test/diag. test/diag. invalid message received request selftest result selftest response rd rd wr 0 0 1 1 1 1 1 1 0 0 0 0 0 1 0 1 0 0 1 0 0 1 0 0 40h 40h inv 0 1 0 0 0 pro dro prr mb1 mb0 0 0 0 1 1 0 0 0 1 channel 0 configuration setup wr 0 0 0 0 0 0 0 mce nom monitor channel mam mra 0 0 0 slin csel 0 0 0 1 0 0 0 1 channel 0 configuration request wr 0 monitor channel 0 0 0 1 1 0 0 0 1 channel 0 configuration response rd 3 monitor channel 0 0 0 0 0 0 0 mce mam mra 0 0 0 slin csel 0 0 1 1 0 0 0 0 channel 0 receive data rd monitor channel - med msd - - - - - nom 1st data byte 2nd data byte ... data bytes 0 0 1 1 0 0 0 0 channel 0 transmit data wr monitor channel 0 med msd 0 0 0 0 0 nom 1st data byte 2nd data byte ... data bytes 0 0 1 1 0 0 1 0 channel 0 status event rd monitor channel mevt 0 svnh test/diag. soft reset wr 0 0 1 0 1 0 0 0 rcmd 0 7115_73 2 0 evtl - - - - - evth 0 0 1 0 0 1 0 0 0 0 1 0 0 1 0 1 test/diag. test/diag. cvnl chip version request wr 00 chip version response rd 2 cvnh the following two messages are not defined after the dsp program download is finished: 0 0 0 1 0 1 0 1 0 gpio output register set/reset wr 4 gpio open drain select wr 20h 4 gpio strobed input 30h 4 gpio direction select 0 gpio interrupt mask gpio status request wr 40h 0 4 0 gpio status event/message rd 02 4 channel 0 channel 0 channel 0 channel 0 channel 0 channel 0 general purpose ios general purpose ios general purpose ios general purpose ios general purpose ios general purpose ios channel 0 general purpose ios 0 0 1 0 1 0 1 0 0 0 1 0 1 0 1 0 0 0 1 0 1 0 1 0 0 0 1 0 1 0 1 0 0 0 0 0 1 0 1 0 0 0 1 0 1 0 1 0 wr wr wr 10h r(7:0) s8 r8 s(7:0) st(7:0) st8 in(7:0) out8 in8 out(7:0) od(7:0) pp8 od8 pp(7:0) c(7:0) s8 c8 s(7:0) rm(7:0) sm8 rm8 sm(7:0)
psb 7115 example configuration settings semiconductor group 243 02.98 5 example configuration settings to give a better understanding how to program each of the parameters, some examples are given below for each of the functional blocks. the mechanism to transfer messages from the host to the isar 34 is described in chapter 3.1.5 . it should be noted, that the host interrupt status register (his) must only be written as the last register access for the message. buffer configuration set channel 1 to buffer base priority 5 and maximum message length of 32: control reg. msb = 05h control reg. lsb = 01h 1. parameter = 20h his = 64h set channel 2 to buffer base priority 3 without changing the maximum message length: control reg. msb = 03h control reg. lsb = 0 no parameters his = a4h set channel 2 to maximum message length 32 without changing the buffer base priority: control reg. msb = 0 control reg. lsb = 1 1. parameter = 20h his = a4h sart configuration set channel 1 to hdlc mode with regular i/o, 1 as interframe fill and 16 bit fcs length. in case of data underrun, fcs and final flag should be generated automatically (tx direction): control reg. msb = 03h control reg. lsb = 01h 1. parameter = 09h his = 65h set channel 2 to v.14 mode (synchronous modulation) with overspeed range "1 of 4", even parity, two stop bits, 6 bit character size and a buffer flush timeout of 32: control reg. msb = 02h control reg. lsb = 02h 1. parameter = 5dh 2. parameter = 20h his = a5h
psb 7115 example configuration settings semiconductor group 244 02.98 pump configuration set channel 1 to faxmodulations in originating mode, 6 db transmitter output attenuation, calling tone enabled, carrier on detect duration of 800 ms and carrier loss detect duration of 2000 ms: control reg. msb = 81h control reg. lsb = 04h 1. parameter = 01h 2. parameter = 06h 3. parameter = 08h 4. parameter = 14h his = 66h important note: if the pump is set to faxmodulations, the sart must not be configured as this is controlled by fax control commands which support implementation of fax class1 (see chapter 3.13 fax class 1 implementation). set channel 1 to automode data modulation in answering mode with 8 db transmitter output attenuation with answer tone enabled and all modulation schemes are disabled except v.32bis with data rates up to 12000 bit/s only. v.8 is disabled, the carrier on detect duration is 600 ms and carrier loss detect duration is 1400 ms: control reg. msb = 42h control reg. lsb = 0bh 1. parameter = 0 2. parameter = 82h 3. parameter = 0fh 4. parameter = f1h 5. parameter = 0 6. parameter = 0 7. parameter = 02h 8. parameter = 0 9. parameter = 08h 10. parameter = 06h 11. parameter = 0eh his = 66h
psb 7115 example configuration settings semiconductor group 245 02.98 iom a -2 configuration set channel 1 to the first timeslot on the iom-2 interface with 8-bit timeslot length and regular switching of tx/rx paths. pcm data is a-law encoded and rate conversion is enabled (typical iom-2 configuration for pump modes fax, datamodem and halfduplex modulations): control reg. msb = 83h control reg. lsb = 05h 1. parameter = 10h 2. parameter = 0 3. parameter = 0 4. parameter = 0 5. parameter = 0 his = 67h set channel 2 to the third timeslot on the iom-2 interface with 8-bit timeslot length and mapping of transmitter and receiver to dd and du of iom-2 respectively. pcm data is m -law encoded. this configuration might be used e.g. for pump mode dtmf: control reg. msb = 84h control reg. lsb = 05h 1. parameter = 08h 2. parameter = 02h 3. parameter = 0 4. parameter = 02h 5. parameter = 0 his = a7h the configuration of the iom-2 interface has to make sure that the selected timeslots for channel 1 and 2 do not overlap, even if one of the channels is currently disabled by setting the iom-bit to 0.
psb 7115 detailed register description semiconductor group 246 02.98 6 detailed register description 6.1 register address map 6.2 register description rst ? isar 34 reset the host resets the isar 34 by writing rst=1 and it is active until this bit is reset again (rst=0). the host must ensure that the reset is active for at least 2 ms, which has the same function as a hardware reset. address read write b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 08h rst rst 07h CCCCC msk CCCCCCCstaCC 06h host control register high isar 34 control register high 05h host control register low isar 34 control register low 04h CCCCCCCiia isar 34 interrupt status (iis) 03h host interrupt status (his) CCCCCCChia 02h mailbox i/o data 01h mailbox write address 00h mailbox read address reset bit read/write address 08h value after reset: xxxx xxx0 76543210 CCCCCCCrst
psb 7115 detailed register description semiconductor group 247 02.98 msk ? interrupt mask all internal interrupt sources can be masked by setting msk to 0. in this case the interrupt is not indicated by activating the interrupt line, however it remains internally stored and pending until the msk bit is set to 1 (i.e. the interrupt is enabled). sta ? interrupt status the sta bit indicates an interrupt status of the isar 34. if set to 1, an internal interrupt is pending. the msb of the control word contains configuration, status or control information, depending on the message specified by the his/iis register. interrupt mask bit write address 07h value after reset: xxxx x1xx 76543210 CCCCCmskCC interrupt status bit read address 07h value after reset: xxxx x0xx 76543210 CCCCC sta C C host/isar 34 control register high write/read address 06h 76543210
psb 7115 detailed register description semiconductor group 248 02.98 the lsb of the control word contains the number of additional bytes in the mailbox, which depends on the message specified by the his/iis register. iia ? isar 34 interrupt acknowledge after reading a complete message from the isar 34 mailbox, the host sets iia to 0 to indicate to the isar 34, that the current message transfer is complete and a new message transfer may be started. the isar 34 interrupt status register (iis) contains the source of the interrupt, i.e. buffer 0, 1, 2 or 3, the kind of indication (configuration, status or received data) and the indication source (buffer, sart, pump or iom-2). host/isar 34 control register low write/read address 05h 76543210 isar 34 interrupt acknowledge bit write address 04h 76543210 CCCCCCCiia isar 34 interrupt status read address 04h 76543210 iis
psb 7115 detailed register description semiconductor group 249 02.98 the host interrupt status register (his) contains the destination of the transferred message, i.e. buffer 0, 1, 2 or 3, the kind of command (request message, configuration, control or transmit data) and the functional block (buffer, sart, pump or iom-2). hia ? host interrupt acknowledge when transfering a message to the isar 34 mailbox, the final write access to the host interrupt register will automatically set the hia bit. the isar 34 will reset hia as soon as the isar 34 is capable to accept another message. the mailbox contains configuration, status and control information in addition to the control register msb as well as transmit and receive data. the number of bytes in the mailbox is indicated in the control register lsb. host interrupt status (his) write address 03h 76543210 host interrupt acknowledge bit read address 03h 76543210 CCCCCCChia mailbox i/o data write/read address 02h 76543210
psb 7115 detailed register description semiconductor group 250 02.98 this register indicates the current write address on the mailbox buffer. before any data is written to the mailbox, the write address must be reset to 0 by the host. for any access to mailbox i/o data, the address pointer will be autoincremented and does not need to be programmed. this is the recommended way for sequential, fast access to the mailbox. for random access, the host has to reprogram the write address pointer. this register indicates the current read address on the mailbox buffer. before the mailbox contents of a message are read, the read address must be reset to 0 by the host. for any access to mailbox i/o data, the address pointer will be autoincremented and does not need to be programmed. this is the recommended way for sequential, fast access to the mailbox. for random access, the host has to reprogram the read address pointer. mailbox write address write/read address 01h 76543210 mailbox read address write/read address 00h 76543210
psb 7115 electrical characteristics semiconductor group 251 02.98 7 electrical characteristics 7.1 absolute maximum ratings note: stresses above those listed here may cause permanent damage to the device. exposure to absolute maximum rating conditions for extended periods may affect device reliability. note: the isar 34 is an esd (electrostatic discharge) sensitive device. electrostatic charges readily accumulate on the human body and equipment and can discharge without detection. permanent damage may occur to devices subjected to high energy electrostatic discharges. 7.2 recommended operating conditions v dd = 3.0 to 3.6 v; v ddp = 4.5 to 5.5 v, v ss = 0 v v dda = 3.0 to 3.6 v, v ssa = 0 v v ddap = 3.0 to 3.6 v, v ssap = 0 v parameter symbol limit values unit ambient temperature under bias t a 0 to 70 c storage temperature t stg C 65 to 125 c supply voltage v dd C 0.3 to 4.2 v supply voltage v dda C 0.3 to 4.2 v supply voltage v ddap C 0.3 to 4.2 v supply voltage v ddp C 0.3 to 6.0 v voltage of pin with respect to ground: xtal1, xtal2 v s C 0.3 to v dda + 0.5 v voltage of any other pin with respect to ground v s if v ddp < 3 v : C 0.3 to v dd + 0.5 if v ddp > 3 v: C 0.3 to v ddp + 0.5 v v
psb 7115 electrical characteristics semiconductor group 252 02.98 7.3 dc characteristics conditions: see above (recommended operating conditions); t a = 0 to + 70 c. all pins except xtal1, xtal2: for the sequence of applying supply voltage to the isar 34 it is necessary that first the v ddp and then the v dd / v dda / v ddap supply is switched on. simultanous ramp up of both supplies is allowed. applying voltages to signal pins when power supply is not active (circuit not under bias) may cause damage. refer to paragraph absolute maximum ratings. when power supply is switched on, the pads do not reach their stable bias until after 2 m s (maximum). parameter symbol limit values unit test condition min. max. high-level input voltage v ih 2.0 v low-level input voltage v il 0.8 v high-level output voltage v oh 2.4 v i oh = C 400 m a low-level output voltage v ol 0.45 v i ol = 7 ma du, dd, ca(0:17), cd(0:15), crd , cwr , csm0-3 , fsc, dcl, intn, sr, st (50 pf) i ol = 2 ma all others (30 pf) input leakage current i li C 10 10 m a0 v < v in < v ddp output leakage current i lo C 10 10 m a0 v < v out < v ddp v dd + v dda + v ddap supply current i dds 150 ma v.34+ connection v ddp supply current i ddps 3 ma v.34+ connection
psb 7115 electrical characteristics semiconductor group 253 02.98 7.4 capacitances 7.5 oscillator circuit figure 68 oscillator circuit 7.6 xtal1,2 recommended typical crystal parameters note: the discrete capacitances c ld depend on the recommended crystal specification. typical values for c ld are 22 ... 33 pf. parameter symbol limit values unit test condition min. max. input capacitance c in 7pf i/o capacitance c i/o 7pf load capacitance c l 20 pf xtal1,2 parameter symbol limit values unit frequency (cm0,1 = 10) f 7.680 mhz frequency (cm0,1 = 01) f 15.360 mhz frequency (cm0,1 = 11) f 16.348 mhz frequency calibration tolerance max. 100 ppm discrete capacitances c ld 33 pf resonance resistor r r 50 w oscillator mode fundamental
psb 7115 electrical characteristics semiconductor group 254 02.98 7.7 ac characteristics 7.7.1 testing waveform conditions as above (recommended operating conditions) at t a = 0 to 70 c. inputs are driven to 2.4 v for a logical 1 and to 0.45 v for a logical 0. timing measurements are made at 2.0 v for a logical 1 and 0.8 v for a logical 0. the ac testing input/output waveforms are shown in the figure below. figure 69 testing input/output waveforms 7.7.2 parallel host interface timing siemens/intel bus mode figure 70 microprocessor read timing
psb 7115 electrical characteristics semiconductor group 255 02.98 figure 71 microprocessor write timing figure 72 multiplexed address timing figure 73 non-multiplexed address timing itt09661 wr x cs or a0-a7 t ah t as address rd x cs
psb 7115 electrical characteristics semiconductor group 256 02.98 motorola bus mode figure 74 microprocessor read timing figure 75 microprocessor write timing figure 76 non-multiplexed address timing itt09679 cs x ds d0 - d7 t dw data t wd dsd t ww tt wi r / w t rwd itt09662 cs x ds ad0 - ad7 t ah t as
psb 7115 electrical characteristics semiconductor group 257 02.98 parameter symbol limit values unit min. max. ale pulse width t aa 50 ns address setup time to ale t al 15 ns address hold time from ale t la 10 ns address latch setup time to wr , rd t als 0ns address setup time t as 25 ns address hold time t ah 10 ns ale guard time t ad 15 ns ds delay after r/w setup t dsd 0ns r/w hold from cs x ds inactive t rwd 0ns rd pulse width t rr 110 ns data output delay from rd t rd 110 ns data float from rd t df 25 ns rd control interval t ri 70 ns w pulse width t ww 60 ns data setup time to w x cs t dw 35 ns data hold time w x cs t wd 10 ns w control interval t wi 70 ns
psb 7115 electrical characteristics semiconductor group 258 02.98 7.7.3 external memory interface timing figure 77 external memory interface - write cycle figure 78 external memory interface - read cycle
psb 7115 electrical characteristics semiconductor group 259 02.98 parameter symbol limit values unit min. max. chip select setup time t sc -2.3 1.0 ns chip select hold time t hc 1.0 ns address setup time write t saw 4.0 ns address hold time after end of write t haw 1.3 ns write pulse width t wp 25.0 ns cwr low to output enable t oe 1.0 ns cwr low to data valid t swr 12.5 ns data hold time t hd 01.0ns read pulse width t rp 38.5 ns address setup time read t sar -4.0 1.0 ns address hold time after end of read t har 1.0 ns data setup time t sd 18.5 ns
psb 7115 electrical characteristics semiconductor group 260 02.98 7.7.4 iom a -2 interface timing figure 79 iom a -2 timing with double rate dcl parameter symbol limit values unit min. max. dcl period t p 244 ns dcl high t wh 100 ns dcl low t wl 100 ns frame sync setup t fss 40 ns frame sync hold t fsh 40 ns output data from high impedance to active t ozd 100 ns output data delay from clock t odd 100 ns output data from active to high impedance t odz 80 ns input data setup t ids 20 ns input data hold t idh 40 ns
psb 7115 package outlines semiconductor group 261 02.98 8 package outlines p-tqfp-144-2 (plastic thin quad flat package) gpp0 5616 sorts of packing package outlines for tubes, trays etc. are contained in our data book package information. dimensions in mm smd = surface mounted device
semiconductor group 262 02.98 psb 7115 index a absolute maximum ratings 251 ac characteristics 254 async mode 46 b binary file structure 206 binary mode 47 block header 210 buffer 43 configuration request 81 configuration response 82 configuration setup 79 control command 84 general status event 90 specific status event 89 status request 85 status response 87 bypass mode 54 c c/i-channel 56 capacitances 253 chip version request 201 response 201 communications interface 39 control registers 67 crystal 29 crystal parameters 253 d datamodem modulations 50 dc characteristics 252 d-channel 56 device architecture 19 dsp program download 206 dtmf 53 e electrical characteristics 251 example configuration settings 243 external memory interface 36 timing 258 f fax class 1 implementation 225 binary reception 233 binary transmission 231 call termination 234 hdlc reception 232 hdlc transmission 230 procedure termination 228 , 234 startup procedure 229 fax modulations 48 file header 208 functional blocks 42 functional description 28 g general purpose i/o interface 37 gpio (general purpose ios) 188 h halfduplex modulations 51 hdlc mode 45 his 62 host communication 60 host interface 31 timing 254 i iis 62 interrupt status byte 62
semiconductor group 263 02.98 psb 7115 index invalid messages 205 iom-2 configuration 55 configuration request 170 configuration response general code 171 path 1 and 2 172 path 3 175 configuration setup path 1 and 2 166 path 3 169 control commands general code 176 path 1 and 2 178 status events 180 iom-2 interface 34 timing 260 l logic symbol 18 m mailbox 39 , 41 message overview 76 message structure 61 message transfer 72 monitor channel 59 buffer configuration and status 181 configuration request 184 configuration response 184 configuration setup 182 rx data 185 status events 187 tx data 186 o operational description 60 oscillator circuit 253 p package outlines 261 physical interfaces 31 pin configuration 20 description 21 pll 30 pump 48 configuration setup bypass mode 126 datamodem modulations 114 dtmf 123 fax modulations 112 halfduplex modulations 118 v.110 121 control command bypass mode 136 c/i-channel 137 datamodem modulations 131 dtmf 135 fax modulations 128 halfduplex modulations 131 v.110 132 status events bypass mode 164 d- and c/i-channel 165 datamodem modulations 157
semiconductor group 264 02.98 psb 7115 index dtmf 163 fax modulations 155 halfduplex modulations 158 v.110 159 status request 139 status response bypass mode 153 datamodem modulations 142 dtmf 152 fax modulations 140 halfduplex modulations 146 pump disabled 154 v.110 148 pump configuration 110 r recommended operating condi- tions 251 register description 246 rejection level 53 reset 68 s sai interface 35 sart 45 configuration setup async 94 binary 97 disable sart 99 hdlc 92 control commands with tx data async 107 binary 109 hdlc 105 status events with rx data async 103 binary 104 hdlc 101 selftest request 203 response 203 software reset 39 , 204 software version request 202 response 202 startup procedures 235 automode operation 236 v.8 negotiation 235 summary of messages 239 system integration 13 t test/diagnostics path 199 testing waveform 254 tic-bus access 57 timer interrupt event 200 on/off 199 twist 53 v v.110 52 v.8 235

▲Up To Search▲

Price & Availability of PSB7115FV21

	To Download PSB7115FV21 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .